commit 98cf7ede083dc0fbb7242c7e557a8a2d5499e135 Author: Nick Mathewson <nickm@torproject.org> Date: Thu Oct 14 12:32:57 2021 -0400 Lower the maximum value for guard-extreme-restriction-percent. The previous value was int32_max, which doesn't really make sense. It's safe to do this, since the effect of getting a high value is just to clamp it at 100%. Closes torspec#66. --- param-spec.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/param-spec.txt b/param-spec.txt index b2882a6..3cf36b2 100644 --- a/param-spec.txt +++ b/param-spec.txt @@ -363,8 +363,9 @@ Table of Contents "guard-extreme-restriction-percent" -- Warn the user if they have configured tor to exclude so many guards that the available guard bandwidth is less than this percentage of the total. - Min: 1. Max: INT32_MAX. Default: 1. - First appeared: 0.3.0 + Min: 1. Max: 100. Default: 1. + First appeared: 0.3.0. MAX was INT32_MAX, which would have no meaningful + effect. MAX lowered to 100 in 0.4.7. "guard-min-filtered-sample-size" -- If fewer than this number of guards is available in the sample after filtering out unusable