Project

General

Profile

Feature #5461

Persistence preset: Tor configuration

Added by Tails about 6 years ago. Updated about 1 year ago.

Status:
Confirmed
Priority:
Elevated
Assignee:
-
Category:
Persistence
Target version:
-
Start date:
Due date:
% Done:

0%

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

Description

Team: ?

It would be great to be able to have persistent Tor settings, e.g. bridges and anything that can be configured via Tor Launcher.

Comments:
  1. This makes sense. If a user wants to use only bridges to connect to the Tor network it makes sense to be able to store their bridges as a persistence option. I currently save my bridges in a text file in the persistent storage and manually enter them into Vidalia, and use the "bridge" parameter when tails first starts booting. There seem to be problems with tordate and tor not connecting quickly enough for the tordate script(s) when using bridges.

Related issues

Related to Tails - Feature #5462: Persistence preset: Tor state Confirmed 08/26/2016
Related to Tails - Feature #10491: Redesign the network configuration and startup Confirmed 06/22/2014
Related to Tails - Feature #14544: Spend software developer time on smallish UX improvements In Progress 08/31/2018
Related to Tails - Feature #8243: Support meek bridges Confirmed 11/08/2014
Related to Tails - Feature #15331: Support automatic bridge retrieval in Tor Launcher (Moat) Confirmed 12/12/2017
Blocks Tails - Feature #8825: Provide default bridges Confirmed 01/30/2015

History

#1 Updated by intrigeri almost 6 years ago

  • Category set to Persistence
  • Starter set to No

#2 Updated by coolnodje over 5 years ago

Especially in a web censored country where https://bridges.torproject.org/ is blocked, it's such a hassle to set up a working Tails (you need to already have an uncensored connection, unlikely for a random user) that you really want to have a persistent Tor setup.

#3 Updated by coolnodje over 5 years ago

I'm willing to help to get this working as it's really the last missing bit to get a usable distrib in my situation.
Where to start? Without any prior knowledge about Tails, from the way it works, I guess the problem is that nothing can be made persistent. If right the question becomes: is there any system that allow for reading external data in place? Could we read a file containing bridges that would be on the USB key, along with the disturb?
If not, then it'd be easy to write the Tor config somewhere on the filesystem, like it's usually done.
Directions welcome.

#4 Updated by intrigeri over 5 years ago

I'm willing to help

Great!

Where to start?

https://tails.boum.org/contribute/how/code/ and
https://tails.boum.org/contribute/design/ :)

Without any prior knowledge about Tails, from the way it works,
I guess the problem is that nothing can be made persistent.

This is not correct:

If someone wants to implement this, I would suggest to start with
a design that stores the list of bridges in a file at the root of the
persistent volume, and uses it to re-configure Tor at login time (see
how the additional software code does something very similar).

Note that the UX needs some care here: if this feature is enabled,
most likely we don't want to run Tor Launcher.

#5 Updated by BitingBird over 5 years ago

  • Subject changed from persistence preset - bridges to Persistence preset - bridges

#6 Updated by intrigeri about 5 years ago

  • Subject changed from Persistence preset - bridges to Persistence preset - Tor configuration
  • Description updated (diff)

#7 Updated by garrettr over 4 years ago

Another use case for Tor configuration persistence would be support for authenticated Tor Hidden Services (ATHS). In order to access an ATHS, you need to add a corresponding "HidServAuth" line to your torrc. It would be nice if we could automatically add such lines to the Tails torrc and reload Tor so it picks them up on boot. I think this could easily be added to the design suggested in #4.

#8 Updated by BitingBird over 4 years ago

  • Subject changed from Persistence preset - Tor configuration to Persistence preset: Tor configuration

#9 Updated by intrigeri over 4 years ago

#10 Updated by anonym over 4 years ago

#11 Updated by anonym over 4 years ago

#12 Updated by sajolida about 4 years ago

  • Description updated (diff)
  • Target version set to 2017

#13 Updated by sajolida almost 4 years ago

  • Related to Feature #10491: Redesign the network configuration and startup added

#14 Updated by kurono almost 4 years ago

  • Assignee set to kurono

#15 Updated by intrigeri over 3 years ago

I'm told that those working on this project will need to have a good look at https://trac.torproject.org/projects/tor/ticket/12600.

#16 Updated by sajolida over 3 years ago

Thanks for the pointer. I subscribed to this ticket and pointed back to our related efforts.

#17 Updated by Dr_Whax about 3 years ago

  • Description updated (diff)
  • Assignee deleted (kurono)
  • Priority changed from Normal to Elevated
  • Target version deleted (2017)

#18 Updated by u about 1 year ago

intrigeri wrote:

I'm told that those working on this project will need to have a good look at https://trac.torproject.org/projects/tor/ticket/12600.

"These tickets, tagged with 034-removed-*, are no longer in-scope for tor 0.3.4. We can reconsider any of them, if time permits."

#19 Updated by sajolida about 1 month ago

  • Related to Feature #14544: Spend software developer time on smallish UX improvements added

#20 Updated by intrigeri about 1 month ago

#21 Updated by intrigeri about 1 month ago

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

Also available in: Atom PDF