4 Commits

Include renames

Author	SHA1	Message	Date
openhands	3e1a3f92c8	feat(security): recovery alerts, gate-block sharing, rolling-window burst and admin breakdown for CrowdSec	2026-09-23 15:06:16 +02:00
openhands	301edd2c9a	feat(security): ops alerts, shared backoff, atomic quota and daily stats for CrowdSec ... Add an alerting/stats layer over the existing CrowdSec integration: - New crowdsec-alerts.ts: cooldown-gated ops alerts (Redis NX lock, TTL from HEALTH_ALERT_COOLDOWN_MIN) fanning out through the app's sendAlert service. Raised for daily quota exhaustion, block bursts (5-min window past CROWDSEC_ALERT_BLOCK_BURST), and signal-push failures. - New crowdsec-stats.ts: daily counters (lookups/blocks/reports/report_fail) in Redis with a 14-day reader for the admin panel. - Shared 403/429 backoff: the pause marker now lives in Redis (crowdsec:backoff-until) so every instance honours it, not just the process that hit the limit. - Atomic quota reservation: INCR-before-call with self-rollback on overshoot, so concurrent instances can never slip calls past the daily ceiling. - Admin anti-DDoS page gains a last-14-days activity table next to the quota bar.	2026-09-23 14:45:35 +02:00
openhands	5e4fc9ab59	feat(security): give back to CrowdSec and harden the CTI budget ... - Bound the in-process verdict cache (FIFO eviction at 2000 entries) so a flood of distinct bucket-tripping IPs cannot grow it without limit. - Record block metadata (reputation, score, behaviors, category, TTL) in antiddos:block:meta:{ip}, surfaced as the reason in the admin block list; unban now also clears the metadata and report locks. - Track daily CTI enrichment usage in Redis (crowdsec:usage:{date}); warn once at 80% and pause lookups until tomorrow at CROWDSEC_CTI_DAILY_QUOTA (default 10000, 0 = unlimited) so a via-spread DDoS cannot burn the plan. - Add opt-in signal push to the CrowdSec community (CAPI watcher): stable auto-generated 48-char machine_id/password pair persisted in Redis (or via env), one-time registration, cached JWT login, optional Console enrollment, and POST /v3/signals with a ban decision, deduped per IP. Never throws and reports last status to the admin panel with a verify action. - Admin page: quota usage bar, reporting status/verify channel, and CrowdSec block reasons in the active-blocks list.	2026-09-23 14:24:44 +02:00
openhands	f32a6dadd0	feat(security): auto-block repeat offenders via CrowdSec community reputation ... - new crowdsec-api lib: CTI lookup (GET /smoke/{ip}, freemium x-api-key), verdict parser with false-positive veto, 1h Redis + in-memory verdict cache, NX lock dedupe, 403/429 backoff; writes only the shared antiddos:block:{ip} key (value "crowdsec") and never touches Cloudflare - gate fires it fire-and-forget for IPs that already tripped a rate bucket, so known-bad IPs are hard-blocked before the local maxViolations threshold - runtime config: crowdsecAutoBlock toggle, score threshold (0-5, default 4), block TTL (default 24h); boot defaults CROWDSEC_AUTO_BLOCK_ENABLED / CROWDSEC_BLOCK_SCORE / CROWDSEC_BLOCK_TTL_SECONDS - admin panel: CrowdSec stat card, verify-connection action, score/TTL settings, CrowdSec source badge in the blocked-IPs list - credentials live in env only (CROWDSEC_API_KEY); block is enforced per-request via proxy on the resolved X-Forwarded-For / CF-Connecting-IP - tests: crowdsec-api unit suite + ddos-guard integration suite (early-block, threshold, cache dedupe, backoff)	2026-09-23 13:03:19 +02:00