Re: [tor-bugs] #32303 [Applications/Tor Browser]: obfs4proxy incompatibility on Android Q

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#32303: obfs4proxy incompatibility on Android Q
-------------------------------------------------+-------------------------
 Reporter:  sysrqb                               |          Owner:  tbb-
                                                 |  team
     Type:  defect                               |         Status:  closed
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:  fixed
 Keywords:  tbb-rbm, tbb-9.0-issues,             |  Actual Points:
  tbb-9.0.1-can, TorBrowserTeam201911R           |
Parent ID:                                       |         Points:  1
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by n8fr8):

 Just so I am clear, you are not relying on our APT library? Do you have
 your build working for all architectures, and loading the binaries from
 the libs directory so as to be properly executable? You can't just put
 them in the /assets folder anymore. All of this unpacking logic is part of
 what the APT library and API provide.

 It seems you've just integrated the obfs4proxy build directly into the tor
 browser build process. Is this driven by a reproducibility requirement, or
 just a "how we do it" decision?

 It would ultimately be better for the community of developers interested
 in using PT's for you to contribute your efforts into helping us update
 and maintain the reusable APT library. This is why we made it, and
 previously PLUTO, in the first place, and spent years investing in working
 out how to port these things and run them on Android and iOS. Given the
 funding for this working came from a shared source, I am sure they would
 also appreciate that, as opposed to a forking of efforts and methods.

 @eighthave / hc's efforts in updating the build process are focused on the
 next step, as we move all the code necessary for making tor-enabled apps
 to shared libraries, and not standalone process executables, as we do now.
 This will be ultimately necessary for your team, so ideally we can align
 efforts here, and work on a shared infrastructure and approach.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32303#comment:21>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs