Persistence preset: Tor configuration
It would be great to be able to have persistent Tor settings, e.g. bridges and anything that can be configured via Tor Launcher.
- 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 to Tails - Feature #5462: Persistence preset: Tor state||Confirmed||2016-08-26|
|Related to Tails - Feature #10491: Redesign the network configuration and startup||Confirmed||2014-06-22|
|Related to Tails - Feature #14544: Spend software developer time on smallish UX improvements||In Progress||2018-08-31|
Related to Tails -
|Related to Tails - Feature #15331: Support automatic bridge retrieval in Tor Launcher (Moat)||In Progress||2017-12-12|
|Blocks Tails - Feature #8825: Provide default bridges||Confirmed||2015-01-30|
#2 Updated by coolnodje 2014-05-07 02:17:29
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 2014-05-07 02:23:44
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.
#4 Updated by intrigeri 2014-05-07 16:54:21
> I’m willing to help
> 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.
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.
#7 Updated by garrettr 2015-02-18 19:49:44
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.
#15 Updated by intrigeri 2016-06-10 06:27:32
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.
#18 Updated by Anonymous 2018-08-19 10:23:49
> 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.”