Opened 5 years ago

Last modified 4 years ago

#7945 new task

Modify facilitator to hand out multiple relays.

Reported by: aallai Owned by: dcf
Priority: Medium Milestone:
Component: Archived/Flashproxy Version:
Severity: Keywords:
Cc: dcf@… Actual Points:
Parent ID: #10711 Points:
Reviewer: Sponsor:

Description

Currently the facilitator can only give out one relay address to proxies that request clients. Modify it to be able to give out multiple relays, and figure out aspects like load balancing, preferring fast relays, etc.

In the short term (the lifetime of a circuit?), a client needs the same relay. This is because switching relays will change the websocket bridge's fingerprint, which Tor will not tolerate. We need to consider this when a proxy goes down and the client is given a new one.

Child Tickets

Change History (3)

comment:1 in reply to:  description Changed 5 years ago by arma

Replying to aallai:

In the short term (the lifetime of a circuit?), a client needs the same relay. This is because switching relays will change the websocket bridge's fingerprint, which Tor will not tolerate. We need to consider this when a proxy goes down and the client is given a new one.

Alas, it's longer than the lifetime of the circuit. It's basically the lifetime of the Tor client process using that bridge.

See #4624 and its subticket #3292. They appear stalled because nobody has worked out what exactly the behavior should be. For #3292 in this case I think it would be sufficient to just have a torrc option to tell Tor not to care about bridge fingerprints.

Or maybe an option on the bridge line itself, to specify that you don't want it to check the fingerprint once it knows it? That approach seems a bit less klunky.

comment:2 Changed 5 years ago by dcf

Priority: minornormal

comment:3 Changed 4 years ago by infinity0

Parent ID: #10711
Note: See TracTickets for help on using tickets.