HTTP hidden services and other short-lived protocols do not need to keep their circuits open very long. Somewhere between 10min and 1 hour ought to be plenty. Since long-lived circuits are a vector for guard discovery (see legacy/trac#22728 (moved)), we should provide a torrc option to set a max hidden service circuit lifetime.
Note that making this timeout too low effectively enables new forms of legacy/trac#20212 (moved), so we should err towards an hour for the timeout here until that fix is landed.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
After a certain number of bytes (like a multiplier of a website's expected page size) have been sent on the circuit. Read and write should be separate params, since many services have much more data going in one direction than the other.
After the vanguard/pinned middle stops being used.
Trac: Summary: Provide torrc option to kill hidden service circuits after $TIMEOUT to Provide torrc option to kill hidden service circuits after $TIMEOUT, $NUM_BYTES, or guard changes.