From 3a9c67fa7ba5ab319bc9485224effeb623ecd422 Mon Sep 17 00:00:00 2001 From: clawbot <35+clawbot@noreply.example.org> Date: Thu, 19 Nov 2026 09:45:32 +0000 Subject: [PATCH] docs: bound the AbuseIPDB bans by the clients listed over the ban days SPEC.md and the README said the bans for AbuseIPDB's blacklist are bounded by the blacklist. Each listed client stays banned for SWW_WAF_ABUSEIPDB_BAN_DAYS, so the bans held are those of every client listed over that time, which can be many more than one blacklist holds. Model: opus-5-5 --- README.md | 3 ++- SPEC.md | 5 +++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 52cbcd6..7810210 100644 --- a/README.md +++ b/README.md @@ -632,7 +632,8 @@ status for a size or time limit, such as `413` for a body too large. - Each limit is counted over a sliding window with a few integers per client. The table of clients and the bans for limits and attacks each have a bound (`SWW_WAF_MAX_TRACKED_CLIENTS`, `SWW_WAF_MAX_BANS`). The bans for AbuseIPDB's - blacklist are bounded by the blacklist. So memory is bounded too. + blacklist are bounded by the clients it listed over the last + `SWW_WAF_ABUSEIPDB_BAN_DAYS` days. So memory is bounded too. - A ban refuses every request from its netblock until it ends. Requests refused under a ban count toward no limit. A permanent ban ends only when an admin lifts it. diff --git a/SPEC.md b/SPEC.md index 25f3373..ea48748 100644 --- a/SPEC.md +++ b/SPEC.md @@ -241,8 +241,9 @@ apply. `SWW_WAF_MAX_TRACKED_CLIENTS`, the least recently seen client is dropped first, with its history. The bans for broken limits and clear signs of attack are bounded by `SWW_WAF_MAX_BANS` (see "Bans"). Those for AbuseIPDB's - blacklist are bounded by the blacklist (see "Reputation"). The GeoJS answers, - the reputation verdicts and scores, the DNS queries under way and the anomaly + blacklist are bounded by the clients it listed over the last + `SWW_WAF_ABUSEIPDB_BAN_DAYS` days (see "Reputation"). The GeoJS answers, the + reputation verdicts and scores, the DNS queries under way and the anomaly counters have fixed bounds, listed under "Fixed limits" in `docs/settings.md`. Past its bound, the GeoJS answer or anomaly counter used longest ago goes first, and the verdict or score fetched longest ago. Past the bound on DNS