Compare commits

...
5 Commits
Author SHA1 Message Date
tech d89b0d09a9 Update signed manifest to 7.60.0 2026-10-07 20:29:14 +00:00
tech fa1beeb71d Update signed manifest to 7.59.0 2026-10-07 15:31:33 +00:00
tech 68cc299d16 Update signed manifest to 7.58.0 2026-10-07 11:13:23 +00:00
tech 5657d78e13 Update signed manifest to 7.57.0 2026-10-07 09:48:13 +00:00
tech 0fb24b0e7b Update signed manifest to 7.56.0 2026-10-06 12:36:24 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.55.0", "version": "7.60.0",
"released_at": "2026-10-05T22:43:45+00:00", "released_at": "2026-10-07T20:29:14+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.55.0/argus-wordpress-defence-7.55.0.zip", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.60.0/argus-wordpress-defence-7.60.0.zip",
"sha256": "b9fada51d586fe609fb51856b2835f819f9e43060232385be259a462fcbf5302", "sha256": "f42ceca31bdf8a4384a738769b7627ef336505705e27d0ae8fe66efb6a6a9b00",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": false, "critical": false,
"summary": "* The broader detection introduced in 7.54.0 now raises real alerts. ARGUS combines several\n independent pieces of evidence about the same file or address -- for example, a suspicious\n request closely followed by a new or changed file -- into one clearly-explained finding,\n instead of treating each piece as a separate, weaker signal.", "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": "+iOec3sJwqOzOn04OvTmXQIEa1dP1jS4mLpTdp+Z7s3lEDD/vYMZjoI7m/CaoTl5O+sVutTa9zl2XeAUX+Q0BA==" "signature": "pbBCsaPJoswbsr45WM2NaWbvPIACHVffHxCm/FC9DYWml9MpGB1zRvIrpCUFhal0J+BRTxjJ4nh/lPY+bTc6AA=="
} }