Deal with Torbutton being integrated into Tor Browser
Upstream ticket: https://trac.torproject.org/projects/tor/ticket/10760
If upstream manages to add a hidden pref to disable it, we should be good. Otherwise, our Unsafe Browser is in trouble.
This change should land in Tor Browser 9.0a1, which should get out end of March/begin of April.
#6 Updated by intrigeri 2019-07-05 09:27:22
- Target version changed from Tails_3.15 to Tails_3.16
> We should coordinate with the Tor Browser team during the 3.15 dev cycle.
I see that anonym did that (https://trac.torproject.org/projects/tor/ticket/10760#comment:44 and https://trac.torproject.org/projects/tor/ticket/10760#comment:45).
Let’s come back to it once the corresponding branch is merged upstream.
#7 Updated by intrigeri 2019-08-30 16:10:21
- Priority changed from Normal to Elevated
- Target version changed from Tails_3.16 to Tails_3.17
> Let’s come back to it once the corresponding branch is merged upstream.
https://trac.torproject.org/projects/tor/ticket/10760 was merged into their master branch (although there are still a few child tickets open). anonym explained there how to test the code. Let’s do this ASAP during the 3.17 cycle!
#8 Updated by intrigeri 2019-09-09 10:30:17
- Type of work changed from Communicate to Research
At first glance, Torbutton works just fine in Tor Browser; I’ve tested the circuit view and the new circuit feature.
But the Unsafe Browser segfaults on startup. I don’t know if that’s related or an entirely different problem.