docs: say SWW_WAF_MAX_BANS bounds only the bans for limits and attacks
check / check (push) Successful in 4m40s
check / check (push) Successful in 4m40s
The bans for AbuseIPDB's blacklist do not count toward SWW_WAF_MAX_BANS, but SPEC.md and the README still said it bounds the bans and so the memory, docs/settings.md still called it all of waf's own bans, and the size of bans.json in docs/state-files.md left out the 10,000 or more bans a free account's blacklist adds. Model: opus-5-5
This commit is contained in:
1 parent
3060788ca3
commit
b10986eae1
4 files changed
+16
-12
No files matched your search
@@ -630,8 +630,9 @@ status for a size or time limit, such as `413` for a body too large.
|
||||
- A client is one IPv4 address or one IPv6 netblock of
|
||||
`SWW_WAF_IPV6_GROUP_PREFIX`, since one abuser usually controls a whole /64.
|
||||
- Each limit is counted over a sliding window with a few integers per client.
|
||||
The table of clients and the table of bans each have a bound
|
||||
(`SWW_WAF_MAX_TRACKED_CLIENTS`, `SWW_WAF_MAX_BANS`), so memory is bounded too.
|
||||
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.
|
||||
- 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.
|
||||
|
||||
Reference in new issue
Block a user