Compare commits

...
1 Commits
Author SHA1 Message Date
tech 85997bca02 Update signed manifest to 7.63.0 2026-10-08 06:48:52 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "7.62.0",
"released_at": "2026-10-07T21:41:57+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.62.0/argus-wordpress-defence-7.62.0.zip",
"sha256": "67965da074b92518297d7da22a24f4d954ae03ecea3be948b235dc4ab60ded5c",
"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",
"min_php": "7.4",
"min_wp": "6.0",
"critical": false,
"summary": "* Monitor Mode no longer creates a separate finding for every bot signature or attacking IP it\n observes -- they now roll up into a single \"ARGUS is in Monitor Mode\" finding, so switching to\n Block Mode is one decision instead of dozens.\n* In Monitor Mode, a detected credential-stuffing attempt is no longer banned behind the scenes --\n like every other Monitor Mode detection, it is now only observed and counted in the Monitor Mode\n finding above, until you switch to Block Mode.",
"signature": "6/F/eRCZAaf1dJeNSBHeXNVXY9HHlXqUnt0l7CmML19iJtwOAtOg0zJcPqJDoXOsuzNrqyQX3+xPJbzpq6AIAg=="
"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=="
}