Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
1544198d02 | ||
|
|
4b3e877127 | ||
|
|
8324647177 | ||
|
|
eec9b0e6f0 | ||
|
|
301e39dc66 | ||
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda | ||
|
|
2ce45b9c2d | ||
|
|
21ed592b8b | ||
|
|
cc56098488 | ||
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 | ||
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 | ||
|
|
d89b0d09a9 | ||
|
|
fa1beeb71d |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.58.0",
|
||||
"released_at": "2026-10-07T11:13:22+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.58.0/argus-wordpress-defence-7.58.0.zip",
|
||||
"sha256": "b140d997084875edafa67a4762f3f7ec5662c17cbf9670a024b092351e950a90",
|
||||
"version": "7.72.0",
|
||||
"released_at": "2026-10-31T18:02:18+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.72.0/argus-wordpress-defence-7.72.0.zip",
|
||||
"sha256": "70783c157302fe7bd6be6106b310a564c5e0e3e1b33652a1806b897023988d5e",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* Findings for events ARGUS already handled automatically -- a brute-force IP ban, a bad-bot\n auto-block -- now consistently say so, instead of occasionally still showing \"Nothing\n automatically\" after the action already happened.\n* If an automatic ban ever fails to save, ARGUS now raises its own finding about that failure\n instead of quietly treating the event as resolved.\n* Vulnerability Protection now recognises ARGUS WordPress Defence itself as a trusted, first-party\n component, instead of showing it as an unverified external plugin just because it isn't\n distributed through WordPress.org. A real vulnerability in ARGUS's own code is still detected\n and flagged just the same.",
|
||||
"signature": "1DvPQAaVW591I8ZNfz4ZVl0xTsJOOzRy1NCcrl3k6vizqbsrG4kvJd3O5lDLD23Q5VsFrUlM5BT/vatxN7soDQ=="
|
||||
"summary": "* ARGUS now acts on security findings it accumulates over time, not just individual requests.\n Findings from distributed scans that spread across many source addresses are automatically\n resolved once enough evidence builds up. Persistent medium and high-severity findings from a\n single address are also resolved automatically if the problem is not addressed within a few days.\n Low-severity signals that have been quiet for two weeks are quietly archived.\n* When the site mode is changed from Monitor to Block or Strict, ARGUS now closes the \"observing\n only\" status notice immediately instead of waiting up to a week for it to age out on its own.",
|
||||
"signature": "+pJ8yAOQFQi03pirubDZpU6qcdjWzOUi0j2XRjH/KnPhA7gc0qN6Ha9gjsjrXLCwpOLixviQ2WnXs6YaJ6b6Aw=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user