Compare commits

...
2 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
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "7.58.0",
"released_at": "2026-10-07T11:13:22+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.58.0/argus-wordpress-defence-7.58.0.zip",
"sha256": "b140d997084875edafa67a4762f3f7ec5662c17cbf9670a024b092351e950a90",
"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": "* Findings for events ARGUS already handled automatically -- a brute-force IP ban, a bad-bot\n auto-block -- now consistently say so, instead of occasionally still showing \"Nothing\n automatically\" after the action already happened.\n* If an automatic ban ever fails to save, ARGUS now raises its own finding about that failure\n instead of quietly treating the event as resolved.\n* Vulnerability Protection now recognises ARGUS WordPress Defence itself as a trusted, first-party\n component, instead of showing it as an unverified external plugin just because it isn't\n distributed through WordPress.org. A real vulnerability in ARGUS's own code is still detected\n and flagged just the same.",
"signature": "1DvPQAaVW591I8ZNfz4ZVl0xTsJOOzRy1NCcrl3k6vizqbsrG4kvJd3O5lDLD23Q5VsFrUlM5BT/vatxN7soDQ=="
"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=="
}