Project

General

Profile

Bug #11535

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

Added by Anonymous about 3 years ago. Updated 11 months ago.

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

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

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


Related issues

Related to Tails - Feature #8825: Provide default bridges Confirmed 01/30/2015
Related to Tails - Feature #15331: Adapt to Tor's Sponsor4 Tor Launcher UX improvements: moat Confirmed 12/12/2017

History

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

#2 Updated by intrigeri about 3 years ago

  • Priority changed from Normal to Low

Lowering priority for the reasons stated by mercedes508.

#3 Updated by u over 1 year ago

#4 Updated by intrigeri over 1 year ago

  • Related to Feature #15331: Adapt to Tor's Sponsor4 Tor Launcher UX improvements: moat added

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

#6 Updated by u 11 months ago

Is it still present in 3.9?

#7 Updated by intrigeri 11 months ago

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

Also available in: Atom PDF