Opened 23 months ago

Last modified 17 months ago

#28679 new enhancement

Bridge connections on startup

Reported by: sve Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-bridge, censorship, needs-proposal, 041-proposed, ex-sponsor-19, ex-sponsor19
Cc: gk Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


When custom list of bridges is used at startup tor connects to all of them and then selects a random bridge. I find this approach to be less secure than just randomly selecting a bridge and connecting to it, without pre-testing of all bridges, and then select another if previous is unreachable. It's better to have a config option to control this.

Child Tickets

Change History (6)

comment:1 Changed 23 months ago by nickm

Milestone: Tor: 0.4.0.x-final

comment:2 Changed 23 months ago by teor

Keywords: needs-proposal added; proposal removed
Version: Tor:

comment:3 Changed 22 months ago by gk

Cc: gk added

comment:4 Changed 22 months ago by nickm

Keywords: 041-proposed added
Milestone: Tor: 0.4.0.x-finalTor: unspecified
Sponsor: Sponsor19-can

comment:5 Changed 17 months ago by gaba

Keywords: ex-sponsor-19 added

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

comment:6 Changed 17 months ago by gaba

Keywords: ex-sponsor19 added
Sponsor: Sponsor19-can

Remove sponsor 19 and add a keyword ex-sponsor19 to mark all the tickets that could have been in the scope of the sponsor.

Note: See TracTickets for help on using tickets.