Compare commits

..
4 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
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "7.56.0",
"released_at": "2026-10-06T12:36:23+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.56.0/argus-wordpress-defence-7.56.0.zip",
"sha256": "c6a8bb73b91943e69bde39d7ebce5d1ea9670f20e13824f99dd8dd74c9052906",
"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",
"min_php": "7.4",
"min_wp": "6.0",
"critical": false,
"summary": "* Every finding now clearly states whether ARGUS already took action and exactly what it did,\n instead of folding that into the general advice text.\n* A file ARGUS automatically quarantines now shows its own distinct status until you decide\n whether to restore or permanently delete it, instead of looking identical to an untouched,\n unreviewed finding.\n* Correlation-based findings now explain what was found in plain language.\n* Form Protection can now recognise business-inquiry submissions with inconsistent details --\n for example a personal email address on a form that asked for a company name, an email that\n doesn't match the stated company, or a generic, templated-sounding message -- and raises them\n for your review instead of letting them through unnoticed.",
"signature": "f+9T5Dzv/M0RwXtiEi9K6haHUxgVwwyyGAeEmkPqc7LqDocuSVQMXfuggtjprc3HTpc3TRxuNjUP+uFao9pfDg=="
"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=="
}