Opened 7 years ago

Last modified 22 months ago

#4850 new enhancement

Build multiple circuits and use the fastest?

Reported by: hellais Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs needs-design needs-insight needs-analysis
Cc: rransom Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


This mostly applies to a usecase such as tor2web where you have a lot of requests in a certain time frame. It might be a good idea to have more than one active circuit towards a certain hidden service (the top 10).

By building more than one circuit towards a hidden service you are then able to collect some benchmark data with all your active circuits and determine which are the fastest ones and which are the slowest.

The benchmark collection and optimization of circuits by speed could be useful also for the normal user of Tor HS, however it might have some bad anonymity consequences.

Q: Is it a bad idea to discard slow circuits towards Tor HS and keep only fast ones?

notes: Keep in mind that you have no control over the circuit on the Hidden Service side and that building a new circuit takes quite a lot of time.

Q: What privacy implications does such a feature have?

Child Tickets

Change History (4)

comment:1 Changed 7 years ago by nickm

Milestone: Tor: unspecified

comment:2 Changed 6 years ago by nickm

Keywords: tor-hs added

comment:3 Changed 6 years ago by nickm

Component: Tor Hidden ServicesTor

comment:4 Changed 22 months ago by nickm

Keywords: needs-design needs-insight needs-analysis added
Severity: Normal
Summary: Multiple circuit building optimizationBuild multiple circuits and use the fastest?

Q: What privacy implications does such a feature have?

This is the big hangup for any implementation here -- it would need some really serious design and analysis to figure out whether it's safe to do.

Note: See TracTickets for help on using tickets.