Bug #11535

Fail at setting Tor bridge mode when using Unsafe Browser to get bridges

Added by Anonymous 2016-06-16 10:13:41 . Updated 2018-08-17 16:12:55 .

Status:
Confirmed
Priority:
Low
Assignee:
Category:
Tor configuration
Target version:
Start date:
2016-06-16
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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

then:

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

Subtasks

Related issues

Related to Tails - Feature #8825: Provide default bridges Confirmed 2015-01-30
Related to Tails - Feature #15331: Support automatic bridge retrieval in Tor Launcher (Moat) In Progress 2017-12-12

History

#1 Updated by mercedes508 2016-07-17 05:23:16

  • 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.

#2 Updated by intrigeri 2016-07-18 05:53:12

  • Priority changed from Normal to Low

Lowering priority for the reasons stated by mercedes508.

#3 Updated by Anonymous 2018-01-19 16:33:48

#4 Updated by intrigeri 2018-02-26 13:27:32

  • related to Feature #15331: Support automatic bridge retrieval in Tor Launcher (Moat) added

#5 Updated by intrigeri 2018-02-26 13:30:08

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 Feature #15331 or Feature #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.

#6 Updated by Anonymous 2018-08-17 15:40:38

Is it still present in 3.9?

#7 Updated by intrigeri 2018-08-17 16:12:55

I don’t think we’ve changed anything in this area since I last reproduced the problem on 3.5.