Clarify MaxCircuitDirtiness behavior with hidden services. Bug 5259.

This commit is contained in:
Nick Mathewson
2012-05-15 11:22:06 -04:00
parent 5905a0b2db
commit 8e07798284
2 changed files with 6 additions and 2 deletions
+3
View File
@@ -0,0 +1,3 @@
o Documentation fixes:
- Clarify the behavior of MaxCircuitDirtiness with hidden service
circuits. Fix for issue 5259.
+3 -2
View File
@@ -651,8 +651,9 @@ The following options are useful only for clients (that is, if
**MaxCircuitDirtiness** __NUM__::
Feel free to reuse a circuit that was first used at most NUM seconds ago,
but never attach a new stream to a circuit that is too old. (Default: 10
minutes)
but never attach a new stream to a circuit that is too old. For hidden
services, this applies to the __last__ time a circuit was used, not the
first. (Default: 10 minutes)
**NodeFamily** __node__,__node__,__...__::
The Tor servers, defined by their identity fingerprints or nicknames,