Compare commits

..
5 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
+7 -7
View File
@@ -1,11 +1,11 @@
{
"version": "7.64.0",
"released_at": "2026-10-08T07:51:53+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.64.0/argus-wordpress-defence-7.64.0.zip",
"sha256": "61cfa4d5f06e158f4c45233393bbb428c17877111cdc44f8858f0ea210889eea",
"version": "7.69.0",
"released_at": "2026-10-19T13:37:38+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",
"sha256": "d1c006de4e32d83d929285c6768633a4c1f21067560bb9a2c24280021e0d9014",
"min_php": "7.4",
"min_wp": "6.0",
"critical": false,
"summary": "* Closed a narrower follow-up gap in 7.63.0: an IP that was banned shortly after some failed login\n attempts could still get a duplicate \"suspicious behavior\" finding, because the failed attempts\n that led to the ban were being counted as separate new evidence. A genuinely unresolved attempt\n that never actually got banned is unaffected and still shows up for your review, as before.",
"signature": "4OnNOph3V6legWOe/rdi9c3LUANDxKrAvSFg/OKAt3lkRK/zP1Ev7IU2BhqwbBUshmT/0osmzo4k7AluTXdCCA=="
"critical": true,
"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": "T78BKVQ08ouM8bqvKryZ3AN8SxAY+sySZfdBeCJA6jlsJMZO7GrHsnyRnyQ/lh2AcEUXiz9AiHr/syIIe5CDDw=="
}