Opened 8 months ago

Last modified 6 months ago

#31878 new task

Make BridgeDB and bridge authority more resilient

Reported by: phw Owned by:
Priority: Medium Milestone:
Component: Circumvention/BridgeDB Version:
Severity: Normal Keywords: s30-o24a5
Cc: phw, gman999, cohosh Actual Points:
Parent ID: #31281 Points: 10
Reviewer: Sponsor: Sponsor30-must

Description

We should explore options to decentralise BridgeDB and/or our bridge authority.

Child Tickets

Change History (4)

comment:1 Changed 6 months ago by gman999

gman999 into the cc

comment:2 Changed 6 months ago by cohosh

Cc: gman999 cohosh added

comment:3 Changed 6 months ago by phw

Cc: gman999 cohosh removed
Summary: Look into making BridgeDB more resilientMake BridgeDB and bridge authority more resilient

gman999 thought about setting up two bridge authorities behind a single, virtual IP address. This will make our bridge authority more resistant to hardware failure because if one goes down, there's still the other one that continues operations.

Once set up, both bridge authorities would then separately sync their bridge descriptors to BridgeDB, which expects a single directory of bridge descriptors, so we will either have to 1) teach BridgeDB (and Tor Metrics) how to handle >1 directory of bridge descriptors, or 2) write a tool that takes as input an arbitrary number of directories containing bridge descriptors and then produce as output a combined "view" of these descriptors. We agreed to first take a look at a tool that can combine "views" because it would simplify our processing pipeline and it may be easy to do with Stem.

comment:4 Changed 6 months ago by phw

Cc: gman999 cohosh added
Note: See TracTickets for help on using tickets.