Compare commits

...
2 Commits
Author SHA1 Message Date
tech 3aa96c7b3e Update signed manifest to 7.62.0 2026-10-07 21:41:58 +00:00
tech a8108f9b84 Update signed manifest to 7.61.0 2026-10-07 20:54:26 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "7.60.0",
"released_at": "2026-10-07T20:29:14+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.60.0/argus-wordpress-defence-7.60.0.zip",
"sha256": "f42ceca31bdf8a4384a738769b7627ef336505705e27d0ae8fe66efb6a6a9b00",
"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",
"min_php": "7.4",
"min_wp": "6.0",
"critical": false,
"summary": "* Bot Protection: added Bot Signature Exceptions, so you can review a bot classification once and\n have that decision apply to every future request matching it -- not just one finding. Previously,\n dismissing a single Bot Filter finding never stopped the same signature from being flagged (and\n re-blocked) again on the next hit.\n* Bot Filter findings now have a \"Review Bot Classification\" action that opens Bot Protection with\n the signature already filled in, instead of making you hunt for the right settings page.\n* An exception can optionally be scoped to a specific IP range as well as the User-Agent, for a\n real, publicly-documented crawler (for example Google's own crawl ranges) -- recommended over a\n User-Agent-only exception, since a User-Agent header can be sent by anyone.",
"signature": "pbBCsaPJoswbsr45WM2NaWbvPIACHVffHxCm/FC9DYWml9MpGB1zRvIrpCUFhal0J+BRTxjJ4nh/lPY+bTc6AA=="
"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=="
}