Opened 7 years ago

Closed 4 years ago

Last modified 5 weeks ago

#4849 closed enhancement (wontfix)

Tor Hidden Service circuit timeout

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

Description

It is common to contact frequently a certain set of Tor Hidden Services while you may contact very sporadically others. This is particularly important in the tor2web use case.

Currently Tor circuits have a timeout of 10 minutes. It would be nice to be able to set a timeout setting for tearing down a particular circuit towards a certain hidden service.

There are a few ways of achieving:

1) Having this feature built into Tor Tor will learn what are the most visited tor hidden services and sets a particular keep alive based on statistics collected. This factor would change over time and be always more precise (?) This is probably a bad idea as it requires having a specific purpose use feature into Tor proper (Q: Would this feature be of benefit to regular users?)

2) Having this feature built into TorCtl Currently it is not possible to set the timeout of a particular circuit to a specific time. It would be nice to specify via TorCtl that a certain circuit should live for a certain amount of time. This might not be good because it requires changes to Tor, although just the TorCtl part.

3) Hacking our way into making it work with current Tor It is possible to set a very big timeout (5 years?) through TorCtl for *all* circuits. You can then cycle through the circuits and understand which ones have been alive for your established timeout and kill them. This is cheap to implement and doesn't require modification of current Tor.

Child Tickets

Change History (7)

comment:1 Changed 7 years ago by nickm

Milestone: Tor: unspecified

#2 or #3 would be fine by me. #2 would need a quick proposal. #3 could be a torrc option, I think -- can you not do that today? In either case, it'll be an 0.2.4.x thing or later.

comment:2 Changed 7 years ago by nickm

Keywords: tor-hs added

comment:3 Changed 7 years ago by nickm

Component: Tor Hidden ServicesTor

comment:4 in reply to:  description Changed 6 years ago by arma

Replying to hellais:

Currently Tor circuits have a timeout of 10 minutes. It would be nice to be able to set a timeout setting for tearing down a particular circuit towards a certain hidden service.

What's the use case here? Are you accruing too many parallel circuits and something is going wrong because of it? Or are the hidden services getting overloaded because too many clients are idling after they connect? Or are you worried about anonymity issues in some way?

comment:5 Changed 4 years ago by arma

Should we close this ticket? What was the original goal?

comment:6 in reply to:  5 Changed 4 years ago by hellais

Replying to arma:

Should we close this ticket? What was the original goal?

I believe the original goal was to avoid having to rebuild a new circuit (and I believe also picking a new intro point) when accessing very popular Tor Hidden Services via tor2web.

Time has passed and I'm no longer sure if this makes sense or if there is a better way of achieving the same goal.

comment:7 Changed 4 years ago by nickm

Resolution: wontfix
Status: newclosed

Closing; please reopen if we change our minds.

Note: See TracTickets for help on using tickets.