[tbb-bugs] #32303 [Applications/Tor Browser]: obfs4proxy incompatibility on Android Q
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Nov 7 10:46:00 UTC 2019
#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:
-------------------------------------------------+-------------------------
Changes (by gk):
* keywords: tbb-rbm, tbb-9.0-issues, tbb-9.0.1-can, TorBrowserTeam201911
=> tbb-rbm, tbb-9.0-issues, tbb-9.0.1-can, TorBrowserTeam201911R
* status: needs_revision => closed
* resolution: => fixed
Comment:
Alright, commit 878a3855c2b7fc5146cd8c38d2b25a7ed427c7e9 has the final fix
just for this particular bug. The other two fixes can be found in their
respective tickets (#28803, #32413). The fixup branch I made, before
merging it and adjusting the commit messages where needed, is
`bug_32303_fixup` (https://gitweb.torproject.org/user/gk/tor-browser-
build.git/log/?h=bug_32303_fixup).
Thanks to boklm for helping with the review. We realized it's not clear
why we need the mobile (cross-)compiler for some projects and not others
(why in `gobsaes` and not `ed25519`). And why don't we need that on
desktop platforms?
boklm will file a follow-up ticket to figure that out + write some
documentation for our Go build setup into `README.HACKING` to make that
and similar Go-specific things clear for those working on Go parts.
Additionally, he will file tickets to track the upstreaming of the
go(mobile) patches.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32303#comment:19>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tbb-bugs
mailing list