Compare commits

..
1 Commits
Author SHA1 Message Date
tech c8f8640e4c Update signed manifest to 7.65.0 2026-10-09 10:02:58 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.64.0", "version": "7.65.0",
"released_at": "2026-10-08T07:51:53+00:00", "released_at": "2026-10-09T10:02:57+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", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.65.0/argus-wordpress-defence-7.65.0.zip",
"sha256": "61cfa4d5f06e158f4c45233393bbb428c17877111cdc44f8858f0ea210889eea", "sha256": "b2962ccf1d5108af577f88e1e465476814f4e558bab5788c906b2ff033e57230",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": false, "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.", "summary": "* Extended the 7.63.0/7.64.0 duplicate-finding fix to two more cases: a malware-scanner match, and\n a changed/new file that already has its own file-integrity finding, no longer also create a\n separate, duplicate \"suspicious behavior\" finding through Threat Correlation. A genuinely new,\n unconfirmed file change is unaffected and still raises a finding, as before.",
"signature": "4OnNOph3V6legWOe/rdi9c3LUANDxKrAvSFg/OKAt3lkRK/zP1Ev7IU2BhqwbBUshmT/0osmzo4k7AluTXdCCA==" "signature": "X3O9pKEAZcRYM30txJXzZdCbfL2tt9YDew9Jd4xVqNlQQojQkSQagbAGhZXiVAYocZr+yGJj/PI/noVo6qOZDg=="
} }