Compare commits

..
5 Commits
Author SHA1 Message Date
tech 0b315cc0c7 Update signed manifest to 8.6.4 2026-11-17 13:42:53 +00:00
tech b5d72fecea Update signed manifest to 8.6.3 2026-11-17 13:00:38 +00:00
tech b9d3fba547 Update signed manifest to 8.6.2 2026-11-16 13:56:56 +00:00
tech e37ab80220 Update signed manifest to 8.6.1 2026-11-16 13:53:12 +00:00
tech 47b0d553a5 Update signed manifest to 8.6.0 2026-11-16 12:45:27 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "8.5.0",
"released_at": "2026-11-15T12:39:35+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.5.0/argus-wordpress-defence-8.5.0.zip",
"sha256": "d8a21dd3b764d2a0edaa9d6f5b1e9ead551bbddf811fa5b8bde49770287bdc45",
"version": "8.6.4",
"released_at": "2026-11-17T13:42:52+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.6.4/argus-wordpress-defence-8.6.4.zip",
"sha256": "2a3e8f17a4e1d905e0375ff59e16a1e3ca67783c6d054e33f24ef480957f9dce",
"min_php": "7.4",
"min_wp": "6.0",
"critical": false,
"summary": "- Centralized progressive ban escalation policy: all automated ban paths now use a unified TTL ladder (L1 24h, L2 7d, L3 14d, L4 30d max) with a 90-day recurrence window, matching the WAD engine policy. Repeat offenders are banned for progressively longer durations regardless of which detection subsystem triggered the ban.",
"signature": "VHnvrDa8mOvrQq+V4IbZqj8uyK8NjIT0To/NeuTAdZUwoHvGVZ7IYG9wtYNzydb3gWv61ln0lz0n/1DmfQYICw=="
"summary": "- Improvement: single-class behavioural correlation findings combining failed logins with user-enumeration probes are now automatically tracked and trigger ban escalation instead of appearing as open findings requiring review.\n- Improvement: existing open attack-recon findings are reconciled to Security Tracking on upgrade.",
"signature": "f9M8VgoDF9Re3QMwHmAC3P0xPst57t6TfHXPuXhHLwiIHBWUFQ8f0aG8I4huh2pm5szCQi+DlTIS0zJISlaMBw=="
}