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
@@ -239,13 +239,14 @@ apply.
|
||||
load.
|
||||
- Memory is bounded. When the table of clients holds
|
||||
`SWW_WAF_MAX_TRACKED_CLIENTS`, the least recently seen client is dropped
|
||||
first, with its history. The bans are bounded by `SWW_WAF_MAX_BANS` (see
|
||||
"Bans"). 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 queries under way, a zone is asked at the
|
||||
client's next request.
|
||||
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
|
||||
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
|
||||
queries under way, a zone is asked at the client's next request.
|
||||
|
||||
## Bans
|
||||
|
||||
|
||||
Reference in new issue
Block a user