Opened 5 years ago

Last modified 4 weeks ago

#12600 assigned task

Save retrieved bridge information in our state file

Reported by: asn Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: AffectsTails, tor-pt, 034-triage-20180328, 034-removed-20180328
Cc: isis, sajolida, Samdney Actual Points:
Parent ID: Points: 4.5
Reviewer: Sponsor: SponsorM

Description (last modified by sajolida)

Currently, Tor clients don't remember anything about bridges after a restart.
So for example, if there was a torrc Bridge line without a fingerprint specified, and Tor retrieves the fingerprint from the descriptor, it won't save it on the disk.

Or, if a bridge changed IP:PORT, but we managed to get its new ip:port using the bridge authority (see #12599), we will not save this down either.

Fortunately, Sebastian wrote proposal192 about this issue:
https://gitweb.torproject.org/torspec.git/tree/proposals/192-store-bridge-information.txt

We should re-read the proposal, revise it as needed and implement it.

Child Tickets

Change History (28)

comment:1 Changed 5 years ago by isis

Cc: isis added

comment:2 Changed 4 years ago by isis

Keywords: tails-wants 028-triage added
Milestone: Tor: 0.2.???Tor: 0.2.8.x-final
Owner: set to isis
Points: medium/large
Status: newassigned

comment:3 Changed 4 years ago by isis

Priority: normalmajor

FWIW, Tails wants this because, if they start saving the state file in persistent storage, then it would make it easier for Tails users to use bridges since they wouldn't need to type in the bridge line each time at boot. I'd like to prioritise getting this one done so that we can help them out with that.

comment:4 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

These seem like features, or like other stuff unlikely to be possible this month. Bumping them to 0.2.9

comment:5 Changed 3 years ago by nickm

Sponsor: SponsorS-can

Tagging these bridge- and PT- items as S-can.

comment:6 Changed 3 years ago by nickm

Keywords: tor-pt added

comment:7 Changed 3 years ago by in spatium

Severity: Normal

Tails clients who use Macs want this, but many of them still would have to type bridge lines manually in the "Tails Greeter | Network Configuration" panel. Tails > Application > Configure Persistence is available only if Tails starts from USB disk. This Tails persistence option is unavailable if Tails starts from DVD disk. Tails clients have been filing reports and making complaints for a long time about a persistent bug that prevents Tails starting from USB disk in iMacs and Macs.

This bug appears to be a widespread problem that affects a large number of Tails clients who use iMacs and Macs. Maybe Tails needs some help with this.

www.reddit.com https://www.reddit.com/r/tails/comments/4gi6uj/tails_error_failed_failed_to_show_plymouth_boot/

www.reddit.com [https://www.reddit.com/r/tails/comments/4gjzu5/upgrade_tails_to_23_and_my_usb_wont_restart_again/
]

Last edited 3 years ago by in spatium (previous) (diff)

comment:8 Changed 3 years ago by sajolida

Cc: sajolida added

comment:9 Changed 3 years ago by sajolida

Description: modified (diff)

The link to the proposal in the description of the ticket was pointing to something weird so I changed it. I hope I didn't mess up.

I don't have time to dive into the proposal right now but, at first sight, the related efforts in Tails are:

comment:10 Changed 3 years ago by isabela

Points: medium/large4.5

comment:11 Changed 3 years ago by nickm

Keywords: TorCoreTeam201610 added
Milestone: Tor: 0.2.9.x-finalTor: 0.3.0.x-final

Defer target for these doc fixes to 0.3.0 (though of course they can go into 0.2.9 if they're done on time.)

comment:12 Changed 3 years ago by dgoulet

Keywords: TorCoreTeam201611 added; TorCoreTeam201610 removed

comment:13 Changed 3 years ago by dgoulet

Keywords: TorCoreTeam201612 added; TorCoreTeam201611 removed

Going to December!

comment:14 Changed 3 years ago by dgoulet

Keywords: triage-out-030-201612 added
Milestone: Tor: 0.3.0.x-finalTor: 0.3.1.x-final

Triaged out on December 2016 from 030 to 031.

comment:15 Changed 2 years ago by nickm

Sponsor: SponsorS-can

Clear sponsorS and sponsorU from open tickets in 0.3.1

comment:16 Changed 2 years ago by isis

Milestone: Tor: 0.3.1.x-finalTor: 0.3.2.x-final

Deferring to 0.3.2

comment:17 Changed 2 years ago by nickm

Keywords: triage-out-030-201612 removed

comment:18 Changed 2 years ago by nickm

Keywords: TorCoreTeam201612 removed

comment:19 Changed 2 years ago by nickm

Keywords: 028-triage removed

comment:20 Changed 21 months ago by nickm

Sponsor: SponsorM

comment:21 Changed 21 months ago by nickm

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final

comment:22 Changed 18 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

Mark a lot of assigned/needs_revision tickets as 0.3.4. If you think this should happen in 0.3.3 instead, just let me know?

comment:23 Changed 16 months ago by nickm

Keywords: 034-triage-20180328 added

comment:24 Changed 16 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:25 Changed 16 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

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

comment:26 Changed 9 months ago by Samdney

Cc: Samdney added

comment:27 Changed 7 weeks ago by gaba

Keywords: AffectsTails added; tor-bridge tails-wants removed

comment:28 Changed 4 weeks ago by gaba

Owner: isis deleted
Note: See TracTickets for help on using tickets.