-
feat(gateway): suspicion-score auto-block into the shared block list
Build and Push Docker Image / build-and-push (push) Canceled after 0sRelease / version (push) Canceled after 0sRelease / frontend (push) Canceled after 0sRelease / linux (amd64) (push) Canceled after 0sRelease / linux (arm64) (push) Canceled after 0sRelease / windows (push) Canceled after 0sRelease / macos (push) Canceled after 0sRelease / release (push) Canceled after 0sreleased this
2026-10-03 21:58:06 +03:00 | 51 commits to main since this release- Auto-block (opt-in, admin → Gateway → Blocked clients): the gateway node
blocks public clients whose suspicion score reaches the threshold
(default 70 = two signals) and were active in the last 10 min. Auto blocks
go into the same replicated gateway_blocks table as manual ones
(source "auto", always with a TTL, default 24h). - Never touched: private/LAN, loopback, link-local, CGNAT/Tailscale, the
cluster's own machine IPs and an exempt list. Unblocking an auto block
(by default) adds its range to the exempt list so a false positive is
never repeated; switching auto-block on exempts the admin's public IP. - Score: weak scanner needles (/config.json, /webui/, /actuator, …) only
count when nothing served them; more strong needles; +10 for 3+ probes;
the signals behind the score are returned and shown on hover and in the
auto block's reason. - Blocked-clients list: filter by IP/reason/author, manual/auto, hide
expired; "auto" badge; exempt badge in Top clients. - Policy lives in its own cluster_config key (gateway_autoblock):
GET/PUT /gateway/autoblock; DELETE /gateway/blocks/:id?exempt=true.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01CpNg61mcYTDfiesScpgCxuDownloads
- Auto-block (opt-in, admin → Gateway → Blocked clients): the gateway node