Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 | ||
|
|
d89b0d09a9 | ||
|
|
fa1beeb71d | ||
|
|
68cc299d16 | ||
|
|
5657d78e13 | ||
|
|
0fb24b0e7b | ||
|
|
19957d44b0 | ||
|
|
4054510acc | ||
|
|
a0885f319a | ||
|
|
a8cdbef65a | ||
|
|
806094d6a0 | ||
|
|
0faf78287a | ||
|
|
235169e8ac | ||
|
|
67323f0204 | ||
|
|
f3a00c618b | ||
|
|
d39aa6f9bc |
+6
-6
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.45.0",
|
"version": "7.63.0",
|
||||||
"released_at": "2026-09-17T17:48:04+00:00",
|
"released_at": "2026-10-08T06:48:51+00:00",
|
||||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.45.0/argus-wordpress-defence-7.45.0.zip",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.63.0/argus-wordpress-defence-7.63.0.zip",
|
||||||
"sha256": "5573d65f55fcd2d8f2cdcbdd5b95c116bced0d6b94dc4fd23d7327663f84b554",
|
"sha256": "4185f4d090d6edaafe86952c017bc60b7673dd4b39402740872e1b8167a1abbb",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": false,
|
||||||
"summary": "* Findings that are still open now ask for a short reason before they can be archived, so an\n unaddressed issue is never dismissed by accident -- archiving something already resolved or\n accepted still takes one click, as before.\n* Resolving a finding now shows a clear reminder that ARGUS cannot verify the fix for you.\n* A finding you archived will reopen automatically if ARGUS detects the same underlying issue\n again, instead of staying silently hidden.\n* Added False Positive, Reopen, and Restore actions directly to the local Findings page, matching\n what was already available from your WAD account.",
|
"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": "Eb62HdDUdtvzB1FRYKsTv3pBQLe9J2zlUvIGGaA7sU3aD0mrjmIiG+m2Qm8z/ootgJAjA7i9rdaMjf6Lim3EBg=="
|
"signature": "PWMBZPER9IETw5Vjdvdly578k5fTmd8BQDCMFdejYQJhd8ShkOmni/hmXVQQ4ap6LAiXhXJd7gfkFincqq08Aw=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user