This is an automated email from the git hooks/post-receive script.
nickm pushed a commit to branch main in repository torspec.
commit 836a5fb964e288e8ff20e918abf19df353c245ac Author: Nick Mathewson nickm@torproject.org AuthorDate: Mon May 23 14:57:23 2022 -0400
Try to document the many uses of nf_conntimeout_clients.
(This is largely determined by reverse-engineering tor's current behavior.) --- padding-spec.txt | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/padding-spec.txt b/padding-spec.txt index 9806b2a..471dd74 100644 --- a/padding-spec.txt +++ b/padding-spec.txt @@ -283,10 +283,18 @@ Table of Contents - Default: 14000
* nf_conntimeout_clients - - The number of seconds to keep circuits opened and available for - clients to use. Note that the actual client timeout is randomized - uniformly from this value to twice this value. This governs client - OR conn lifespan. Reduced padding clients use half the consensus + - The number of seconds to keep never-used circuits opened and + available for clients to use. Note that the actual client timeout is + randomized uniformly from this value to twice this value. + - The number of seconds to keep idle (not currently used) canonical + channels are open and available. (We do this to ensure a sufficient + time duration of padding, which is the ultimate goal.) + - This value is also used to determine how long, after a port has been + used, we should attempt to keep building predicted circuits for that + port. (See path-spec.txt section 2.1.1.) This behavior was + originally added to work around implementation limitations, but it + serves as a reasonable default regardless of implementation. + - For all use cases, reduced padding clients use half the consensus value. - Default: 1800