Commit Graph
3 Commits
Author SHA1 Message Date
clawbot 3060788ca3 reputation: name a client on AbuseIPDB's blacklist BlacklistEntry
check / check (push) Failing after 3m48s
The type was named Listed, in a package whose DNSBL verdicts carry a
field Listed and whose blocklists list clients too, so the name alone
did not say which list it was on.

Model: opus-5-5
2026-11-19 08:53:21 +00:00
clawbot da6667957f waf: test the blacklist through the server's own wiring
No test fetched the blacklist through the server: the waf tests handed
clients to the ban code directly, so a wrong key, threshold or URL in
newReputation, or no Blacklisted at all, left every test green.

Model: opus-5-5
2026-11-19 08:47:57 +00:00
clawbot e1ed444e68 waf: ban the clients on AbuseIPDB's blacklist (closes #411)
check / check (push) Failing after 6m25s
While SWW_WAF_ABUSEIPDB_KEY is set, waf fetches AbuseIPDB's blacklist at
the start and every SWW_WAF_ABUSEIPDB_BLACKLIST_REFRESH_INTERVAL_MINS
(60), cut at SWW_WAF_ABUSEIPDB_THRESHOLD (90, from 25 to 100). Each
listed client's netblock gets a ban of SWW_WAF_ABUSEIPDB_BAN_DAYS (30)
with the new cause abuseipdb. The blacklist itself is not kept.

These bans do not count toward SWW_WAF_MAX_BANS, so a 10,000-address
blacklist cannot push out the bans for limits and attacks. Each fetch
forgets the abuseipdb bans that have ended. A netblock with an active
ban is left alone, and so is one whose abuseipdb ban an admin lifted,
until that ban would have ended. Observe mode makes no ban.

Model: opus-5-5
2026-11-19 07:59:24 +00:00