From 8e07798284faba6cc2492ca98e50f2e8bcb70934 Mon Sep 17 00:00:00 2001
From: Nick Mathewson <nickm@torproject.org>
Date: Tue, 15 May 2012 11:22:06 -0400
Subject: [PATCH] Clarify MaxCircuitDirtiness behavior with hidden services.
Bug 5259.
---
changes/bug5259 | 3 +++
doc/tor.1.txt | 5 +++--
2 files changed, 6 insertions(+), 2 deletions(-)
create mode 100644 changes/bug5259
diff --git a/changes/bug5259 b/changes/bug5259
new file mode 100644
index 0000000000..bdada586e9
--- /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 25a440d1bb..5f10f68712 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,
--
GitLab