Opened 8 years ago

Last modified 16 months ago

#2473 new project

Develop a design to support multiple bridge authorities

Reported by: arma Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: needs-proposal, tor-dirauth, bridge, bridge-authority, design-needed, decentralization
Cc: Actual Points:
Parent ID: Points: 20
Reviewer: Sponsor:

Description

The main thing blocking multiple bridge directory authorities right now is that we don't have a design for how it would work. For the normal directory authority design, we want all of them to know about all relays. But for bridge authorities, that would defeat the purpose. So we want some algorithms for distributing bridges over authorities, such that bridge users know where to go to look up a given bridge (probably as a function of its identity fingerprint). Perhaps the algorithm should provide stable answers even as we change the set of bridge authorities, and for clients and bridges running a variety of Tor versions. More generally, we need to figure out what functionality we want and what security properties we should shoot for.

Somebody should start with a proposal, and go from there.

Child Tickets

Change History (7)

comment:1 Changed 8 years ago by arma

Component: Tor RelayTor Directory Authority

comment:2 Changed 7 years ago by karsten

Summary: Project: support multiple bridge authoritiesDevelop a design to support multiple bridge authorities
Type: taskproject

comment:3 Changed 6 years ago by nickm

Keywords: needs-proposal added

comment:4 Changed 6 years ago by nickm

Keywords: tor-auth added

comment:5 Changed 6 years ago by nickm

Component: Tor Directory AuthorityTor

comment:6 Changed 16 months ago by dgoulet

Keywords: tor-dirauth added; tor-auth removed

Turns out that tor-auth is for directory authority so make it clearer with tor-dirauth

comment:7 Changed 16 months ago by nickm

Keywords: bridge bridge-authority design-needed decentralization added
Points: 20
Severity: Normal
Note: See TracTickets for help on using tickets.