aboutsummaryrefslogtreecommitdiff
path: root/param-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2023-10-05 23:30:23 -0400
committerNick Mathewson <nickm@torproject.org>2023-10-05 23:30:23 -0400
commit14a57c66eb4e9ab6724b7d22135c6eac968dddc0 (patch)
tree436d397ba2b2440ddb3bfb24a784e7107c2fcb85 /param-spec.txt
parent98b281544c712d993be14a34b8e01fe676edacf9 (diff)
downloadtorspec-14a57c66eb4e9ab6724b7d22135c6eac968dddc0.tar.gz
torspec-14a57c66eb4e9ab6724b7d22135c6eac968dddc0.zip
Update param-spec to reflect bug #40869.
Diffstat (limited to 'param-spec.txt')
-rw-r--r--param-spec.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/param-spec.txt b/param-spec.txt
index 123cedc..b778512 100644
--- a/param-spec.txt
+++ b/param-spec.txt
@@ -126,6 +126,14 @@ Table of Contents
"maxunmeasuredbw" -- Used by authorities during voting with method 17 or
later. The maximum value to give for any Bandwidth= entry for a router
that isn't based on at least three measurements.
+
+ (Note: from versions 0.4.6.1-alpha up to but not including 0.4.9.1-alpha,
+ there was a bug where Tor authorities would instead look at
+ a parameter called "maxunmeasurdbw", without the "e". Until all
+ relays are running 0.4.9.x or later, then either this parameter
+ must not be set, or it must be set to the same value for both
+ spellings.)
+
First-appeared: 0.2.4.11-alpha
"FastFlagMinThreshold", "FastFlagMaxThreshold" -- lowest and highest