aboutsummaryrefslogtreecommitdiff
path: root/param-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2021-10-14 12:32:57 -0400
committerNick Mathewson <nickm@torproject.org>2021-10-14 12:32:57 -0400
commit98cf7ede083dc0fbb7242c7e557a8a2d5499e135 (patch)
tree903fe7f5444d45bf25e380b3004ffb0400efef7e /param-spec.txt
parent1c9b4235101582e4c9c9233ed4491c6c71f22439 (diff)
downloadtorspec-98cf7ede083dc0fbb7242c7e557a8a2d5499e135.tar.gz
torspec-98cf7ede083dc0fbb7242c7e557a8a2d5499e135.zip
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.
Diffstat (limited to 'param-spec.txt')
-rw-r--r--param-spec.txt5
1 files 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