docs: bound the AbuseIPDB bans by the clients listed over the ban days
check / check (push) Waiting to run
check / check (push) Waiting to run
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:
1 parent
b10986eae1
commit
3a9c67fa7b
2 files changed
+5
-3
No files matched your search
@@ -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
|
||||
|
||||
Reference in new issue
Block a user