[tor-commits] [tor/maint-0.2.2] Clarify MaxCircuitDirtiness behavior with hidden services. Bug 5259.

[nickm@xxxxxxxxxxxxxx]

commit 8e07798284faba6cc2492ca98e50f2e8bcb70934
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Tue May 15 11:22:06 2012 -0400

    Clarify MaxCircuitDirtiness behavior with hidden services. Bug 5259.
---
 changes/bug5259 |    3 +++
 doc/tor.1.txt   |    5 +++--
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/changes/bug5259 b/changes/bug5259
new file mode 100644
index 0000000..bdada58
--- /dev/null
+++ b/changes/bug5259
@@ -0,0 +1,3 @@
+  o Documentation fixes:
+    - Clarify the behavior of MaxCircuitDirtiness with hidden service
+      circuits. Fix for issue 5259.
diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index 25a440d..5f10f68 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -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,

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits