From fa1beeb71d5f4c9f75bf434c3e8832fc92cc2e3a Mon Sep 17 00:00:00 2001 From: Luis Melo Date: Wed, 7 Oct 2026 15:31:33 +0000 Subject: [PATCH] Update signed manifest to 7.59.0 --- manifest.json | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/manifest.json b/manifest.json index 859c4af..5b8b76b 100644 --- a/manifest.json +++ b/manifest.json @@ -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.59.0", + "released_at": "2026-10-07T15:31:32+00:00", + "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.59.0/argus-wordpress-defence-7.59.0.zip", + "sha256": "f9ba43c57d969b71ddd763151a6a2c97a79a9971635deeca57f23c7221b3ee29", "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==" + "critical": true, + "summary": "* A file-integrity finding that was correct when first detected could keep showing as a critical,\n unresolved problem even after a later official ARGUS Defence update made the file match the\n real, signed release again. These findings now re-check themselves against the version you\n actually have installed and clear automatically once that's confirmed -- a genuinely tampered\n file still shows as critical, backed by a fresh check, not a stale one.", + "signature": "tvH0duWx7DbAGMkE1o/54nt6CybrvQCLfWby8fWUtc1tY8ZteJpu40ekDIOf2rbM4qq0VpeILbKbYvyw/HRCDQ==" }