Compare commits

...
5 Commits
Author SHA1 Message Date
tech aed69ceb6e Update signed manifest to 7.70.3 2026-10-20 08:00:48 +00:00
tech 82b525ca1e Update signed manifest to 7.70.2 2026-10-19 20:14:36 +00:00
tech 543bdd58d4 Update signed manifest to 7.70.1 2026-10-19 20:01:49 +00:00
tech 1ff0bdbeca Update signed manifest to 7.70.0 2026-10-19 14:01:51 +00:00
tech 09ac6a1fda Update signed manifest to 7.69.1 2026-10-19 13:49:44 +00:00
+7 -7
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.69.0", "version": "7.70.3",
"released_at": "2026-10-19T13:37:38+00:00", "released_at": "2026-10-20T08:00:47+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.69.0/argus-wordpress-defence-7.69.0.zip", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.70.3/argus-wordpress-defence-7.70.3.zip",
"sha256": "d1c006de4e32d83d929285c6768633a4c1f21067560bb9a2c24280021e0d9014", "sha256": "ecf14ff3b8b526c840ea590388b6f8e058556f88c2196507b14fec2867a34136",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": true, "critical": false,
"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.", "summary": "* Fixed a case where blocking the web server's own address in ARGUS stopped WordPress's scheduled\n tasks, so the site could no longer report to the portal or receive the instruction to unblock\n it. WordPress's own internal scheduler requests are no longer refused by the firewall.",
"signature": "T78BKVQ08ouM8bqvKryZ3AN8SxAY+sySZfdBeCJA6jlsJMZO7GrHsnyRnyQ/lh2AcEUXiz9AiHr/syIIe5CDDw==" "signature": "7A9bLx/FEfNMUKGcA5tNEj1laDF8sQU6qaxJKtY/2N/udf50QFtIWrjwD7DGRjn2CWN8ceOPa3pSbvanNkPxCw=="
} }