Fail at setting Tor bridge mode when using Unsafe Browser to get bridges
how does it happen:
start tails > more > need bridge > login > connect ethernet > tor configuration pop up > open unsafe browser > visit https://bridges.torproject.org > copy bridge data
1: if unsafe browser is closed and bridges are pasted into tor setup configuration after closing unsafe browser > error as in subject
2: if unsafe browser is kept open and bridges are pasted > proceed connecting > then close unsafe browser > NO ERROR
#1 Updated by mercedes508 about 3 years ago
- Subject changed from Unable to save tor setting - please ensure that tor is running! to Fail at setting Tor bridge mode when using Unsafe Browser to get bridges
- Status changed from New to Confirmed
I reproduced that issue with Tails 2.4.
The workaround is pretty easy (don't close unsafe browser until you're connected to Tor), and this case might even be a little corner one because if you use bridges not to tell your ISP of whoever that you use Tor, then getting bridges from the same connection using clearnet is certainly not a good idea.
#5 Updated by intrigeri over 1 year ago
This bug is still here in Tails 3.5 and current devel (i.e. wanna-be 3.6). I think it's caused by
maybe_restart_tor at the end of
/usr/local/sbin/unsafe-browser. I'm surprised that not more users complain. Hopefully #15331 or #8825 will remove the need for this (officially unsupported) use case of the Unsafe Browser.
Now, if someone wants to fix that:
maybe_restart_tor should become a no-op when the Tor Launcher is running.