Преглед на файлове

fix(default-config): off-by-one error in the default thresholds (#701)

I don't know how I missed this in testing.
Xe Iaso преди 2 дни
родител
ревизия
3c1d95d61e
променени са 2 файла, в които са добавени 3 реда и са изтрити 2 реда
  1. 2 2
      data/botPolicies.yaml
  2. 1 0
      docs/docs/CHANGELOG.md

+ 2 - 2
data/botPolicies.yaml

@@ -132,14 +132,14 @@ status_codes:
 thresholds:
   # By default Anubis ships with the following thresholds:
   - name: minimal-suspicion # This client is likely fine, its soul is lighter than a feather
-    expression: weight < 0 # a feather weighs zero units
+    expression: weight <= 0 # a feather weighs zero units
     action: ALLOW # Allow the traffic through
   # For clients that had some weight reduced through custom rules, give them a
   # lightweight challenge.
   - name: mild-suspicion
     expression:
       all:
-        - weight >= 0
+        - weight > 0
         - weight < 10
     action: CHALLENGE
     challenge:

+ 1 - 0
docs/docs/CHANGELOG.md

@@ -40,6 +40,7 @@ And some cleanups/refactors were added:
 - Bump AI-robots.txt to version 1.37
 - Make progress bar styling more compatible (UXP, etc)
 - Add `--strip-base-prefix` flag/envvar to strip the base prefix from request paths when forwarding to target servers
+- Fix an off-by-one in the default threshold config
 
 Request weight is one of the biggest ticket features in Anubis. This enables Anubis to be much closer to a Web Application Firewall and when combined with custom thresholds allows administrators to have Anubis take advanced reactions. For more information about request weight, see [the request weight section](./admin/policies.mdx#request-weight) of the policy file documentation.