docs: bound the AbuseIPDB bans by the clients listed over the ban days
check / check (push) Failing after 1m36s

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
This commit is contained in:
clawbot committed 2026-11-19 09:45:32 +00:00
1 parent b10986eae1
commit 3a9c67fa7b
2 files changed
+5 -3

No files matched your search

+2 -1
View File
@@ -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. - 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 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 (`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 - 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 under a ban count toward no limit. A permanent ban ends only when an admin
lifts it. lifts it.
+3 -2
View File
@@ -241,8 +241,9 @@ apply.
`SWW_WAF_MAX_TRACKED_CLIENTS`, the least recently seen client is dropped `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 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 are bounded by `SWW_WAF_MAX_BANS` (see "Bans"). Those for AbuseIPDB's
blacklist are bounded by the blacklist (see "Reputation"). The GeoJS answers, blacklist are bounded by the clients it listed over the last
the reputation verdicts and scores, the DNS queries under way and the anomaly `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`. 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 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 first, and the verdict or score fetched longest ago. Past the bound on DNS