Compare commits

..
4 Commits
Author SHA1 Message Date
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
tech 50336dfd90 Update signed manifest to 7.64.0 2026-10-08 07:51:54 +00:00
tech 85997bca02 Update signed manifest to 7.63.0 2026-10-08 06:48:52 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "7.62.0",
"released_at": "2026-10-07T21:41:57+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.62.0/argus-wordpress-defence-7.62.0.zip",
"sha256": "67965da074b92518297d7da22a24f4d954ae03ecea3be948b235dc4ab60ded5c",
"version": "7.66.0",
"released_at": "2026-10-15T14:06:21+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.66.0/argus-wordpress-defence-7.66.0.zip",
"sha256": "a1d6796fbce70f75852b76d0a1f95c6ea535240cfae4de728d30ee042826344c",
"min_php": "7.4",
"min_wp": "6.0",
"critical": false,
"summary": "* Monitor Mode no longer creates a separate finding for every bot signature or attacking IP it\n observes -- they now roll up into a single \"ARGUS is in Monitor Mode\" finding, so switching to\n Block Mode is one decision instead of dozens.\n* In Monitor Mode, a detected credential-stuffing attempt is no longer banned behind the scenes --\n like every other Monitor Mode detection, it is now only observed and counted in the Monitor Mode\n finding above, until you switch to Block Mode.",
"signature": "6/F/eRCZAaf1dJeNSBHeXNVXY9HHlXqUnt0l7CmML19iJtwOAtOg0zJcPqJDoXOsuzNrqyQX3+xPJbzpq6AIAg=="
"summary": "* New: ARGUS can now email you when it finds something serious, instead of only showing it on the\n Findings page. Turn it on and set a minimum severity under Settings > Overview > Email Alerts --\n multiple findings in the same few minutes arrive as one digest email, not one email each.\n* Hardened the optional page cache against two cross-visitor cache-sharing risks: a request with\n an unrecognised Host could previously create its own separate cached copy of a page, and a\n tracking link parameter (utm_*, fbclid, gclid, and similar) could in theory end up baked into a\n cached page shared with other visitors. Both are now blocked before the page is cached. Legitimate\n cache-sharing between visitors on the same clean URL is unaffected.",
"signature": "4B4ZbdfBB7RcFMCt+YEWNJQfhspsGxsm9/RIv8p2O40b23Z+o/mwtGShV02wX66PsYUZlVfPoXnYbexMjHOGCw=="
}