Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
7d8aae8b8d | ||
|
|
fc9044d87b | ||
|
|
824e062747 | ||
|
|
9f4627c7c1 | ||
|
|
9647a4c776 | ||
|
|
0f19f0ab30 | ||
|
|
fb6cfa5664 | ||
|
|
26dd83e8bc | ||
|
|
c2eae8801b | ||
|
|
a9f7b6ddf9 | ||
|
|
1a959fcdbb | ||
|
|
81d011d56a | ||
|
|
510eab15b3 | ||
|
|
95cb325dd6 | ||
|
|
6bc43378e2 | ||
|
|
99de067d89 | ||
|
|
85bc2b0123 | ||
|
|
830bc5b38a | ||
|
|
407ae0a5f9 | ||
|
|
4d738638a7 | ||
|
|
7c22b85cdf | ||
|
|
027bdc5d06 | ||
|
|
dad8018345 | ||
|
|
91f73b55b0 | ||
|
|
3d2424a027 | ||
|
|
30acc5c9fe | ||
|
|
ada915a068 | ||
|
|
743bf0c7d8 | ||
|
|
5e682f6788 | ||
|
|
6045d150ca | ||
|
|
3d6fe5a100 | ||
|
|
ea32a2e42e | ||
|
|
9f13bcabc4 | ||
|
|
78dba72fad | ||
|
|
770acaf061 | ||
|
|
2ecef66d62 | ||
|
|
94e572214c | ||
|
|
da64bcaadb | ||
|
|
001bbefa3f | ||
|
|
ef6555a1e4 | ||
|
|
8832cee2da | ||
|
|
0c3ac9e463 | ||
|
|
22b7a76a6e | ||
|
|
1544198d02 | ||
|
|
4b3e877127 | ||
|
|
8324647177 | ||
|
|
eec9b0e6f0 | ||
|
|
301e39dc66 | ||
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda | ||
|
|
2ce45b9c2d | ||
|
|
21ed592b8b | ||
|
|
cc56098488 | ||
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.63.0",
|
||||
"released_at": "2026-10-08T06:48:51+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.63.0/argus-wordpress-defence-7.63.0.zip",
|
||||
"sha256": "4185f4d090d6edaafe86952c017bc60b7673dd4b39402740872e1b8167a1abbb",
|
||||
"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",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* Fixed a real gap in the 7.62.0 Monitor Mode fix: a bot ban or other already-fully-handled event\n could still turn into a second, separate \"suspicious behavior\" finding through Threat\n Correlation, duplicating what the Monitor Mode rollup (or the ban itself) had already covered.\n This no longer happens -- genuinely correlated, multi-signal findings are completely unaffected.",
|
||||
"signature": "PWMBZPER9IETw5Vjdvdly578k5fTmd8BQDCMFdejYQJhd8ShkOmni/hmXVQQ4ap6LAiXhXJd7gfkFincqq08Aw=="
|
||||
"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=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user