diff options
| author | David Goulet <dgoulet@torproject.org> | 2023-10-11 15:47:50 +0000 |
|---|---|---|
| committer | David Goulet <dgoulet@torproject.org> | 2023-10-11 15:47:50 +0000 |
| commit | 82ba302230911cafd8683d345f8e7ee0e3ad7dda (patch) | |
| tree | 8473ae1d8a154bb2b3bf0169e92b0f57db691461 | |
| parent | b914dbe0ab9fb3b595cbe1e5dab55ccfe079f40b (diff) | |
| parent | c94ea1beb00694dcfb3d0439906dcbe7885d5e2f (diff) | |
| download | torspec-82ba302230911cafd8683d345f8e7ee0e3ad7dda.tar.gz torspec-82ba302230911cafd8683d345f8e7ee0e3ad7dda.zip | |
Merge branch 'maxunmeasured_fix_again' into 'main'
Correct the versions in which "maxunmeasur[e]dbw" was fixed
See merge request tpo/core/torspec!172
| -rw-r--r-- | param-spec.txt | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/param-spec.txt b/param-spec.txt index b778512..d8ea80b 100644 --- a/param-spec.txt +++ b/param-spec.txt @@ -127,10 +127,11 @@ Table of Contents 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, + (Note: starting in version 0.4.6.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 + a parameter called "maxunmeasurdbw", without the "e". + This bug was fixed in 0.4.9.1-alpha and in 0.4.8.8. + Until all relays are running a fixed version, then either this parameter must not be set, or it must be set to the same value for both spellings.) |