Compare commits

..
4 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
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.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": "* 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": "* 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=="
}