Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
c8f8640e4c | ||
|
|
50336dfd90 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.63.0",
|
||||
"released_at": "2026-10-08T06:48:51+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.63.0/argus-wordpress-defence-7.63.0.zip",
|
||||
"sha256": "4185f4d090d6edaafe86952c017bc60b7673dd4b39402740872e1b8167a1abbb",
|
||||
"version": "7.65.0",
|
||||
"released_at": "2026-10-09T10:02:57+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.65.0/argus-wordpress-defence-7.65.0.zip",
|
||||
"sha256": "b2962ccf1d5108af577f88e1e465476814f4e558bab5788c906b2ff033e57230",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* Fixed a real gap in the 7.62.0 Monitor Mode fix: a bot ban or other already-fully-handled event\n could still turn into a second, separate \"suspicious behavior\" finding through Threat\n Correlation, duplicating what the Monitor Mode rollup (or the ban itself) had already covered.\n This no longer happens -- genuinely correlated, multi-signal findings are completely unaffected.",
|
||||
"signature": "PWMBZPER9IETw5Vjdvdly578k5fTmd8BQDCMFdejYQJhd8ShkOmni/hmXVQQ4ap6LAiXhXJd7gfkFincqq08Aw=="
|
||||
"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": "X3O9pKEAZcRYM30txJXzZdCbfL2tt9YDew9Jd4xVqNlQQojQkSQagbAGhZXiVAYocZr+yGJj/PI/noVo6qOZDg=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user