Compare commits

...
11 Commits
Author SHA1 Message Date
tech 2ce45b9c2d Update signed manifest to 7.69.0 2026-10-19 13:37:39 +00:00
tech 21ed592b8b Update signed manifest to 7.68.0 2026-10-19 08:50:53 +00:00
tech cc56098488 Update signed manifest to 7.67.0 2026-10-18 12:43:00 +00:00
tech 8fa6153099 Update signed manifest to 7.66.0 2026-10-15 14:06:22 +00:00
tech c8f8640e4c Update signed manifest to 7.65.0 2026-10-09 10:02:58 +00:00
tech 50336dfd90 Update signed manifest to 7.64.0 2026-10-08 07:51:54 +00:00
tech 85997bca02 Update signed manifest to 7.63.0 2026-10-08 06:48:52 +00:00
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
+7 -7
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.58.0", "version": "7.69.0",
"released_at": "2026-10-07T11:13:22+00:00", "released_at": "2026-10-19T13:37:38+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", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.69.0/argus-wordpress-defence-7.69.0.zip",
"sha256": "b140d997084875edafa67a4762f3f7ec5662c17cbf9670a024b092351e950a90", "sha256": "d1c006de4e32d83d929285c6768633a4c1f21067560bb9a2c24280021e0d9014",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": false, "critical": true,
"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.", "summary": "* Fixed a blank page after using Archive, Resolve, Acknowledge and the other actions on a finding\n once you had switched tabs or pages in Findings. You now return to the same tab and page, and a\n refused action is shown as an error instead of a success message.\n* The same threat arriving from many different addresses is now challenged automatically, instead of\n staying \"allowed\" however many addresses it came from. The thresholds are unchanged.\n* The \"Needs Attention\" tab in Findings is now called \"Critical & High\", which is exactly what it\n shows. Medium and low findings stay under \"Active\".\n* If ARGUS cannot apply a block or challenge, you now see a single clear finding about it instead of\n nothing, and a challenge that cannot be issued no longer shows a page nobody can complete.\n* Finding descriptions now say how many different sources a threat came from, rather than implying\n every request came from the most recent address.\n* Findings about a threat that was only \"allowed\" before this fix are closed automatically on update, with their evidence kept, and re-open if the threat comes back unchallenged.",
"signature": "1DvPQAaVW591I8ZNfz4ZVl0xTsJOOzRy1NCcrl3k6vizqbsrG4kvJd3O5lDLD23Q5VsFrUlM5BT/vatxN7soDQ==" "signature": "T78BKVQ08ouM8bqvKryZ3AN8SxAY+sySZfdBeCJA6jlsJMZO7GrHsnyRnyQ/lh2AcEUXiz9AiHr/syIIe5CDDw=="
} }