Compare commits

..
5 Commits
Author SHA1 Message Date
tech 303f31e869 Update signed manifest to 7.23.19 2026-08-10 15:05:44 +00:00
tech 20a2a84ee8 Update signed manifest to 7.23.18 2026-08-10 14:14:25 +00:00
tech 9127b06836 Update signed manifest to 7.23.17 2026-08-10 11:36:11 +00:00
tech 19cb788556 Update signed manifest to 7.23.16 2026-08-10 11:08:03 +00:00
tech e52046437b Update signed manifest to 7.23.15 2026-08-10 10:55:14 +00:00
+7 -7
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.23.14", "version": "7.23.19",
"released_at": "2026-08-10T10:42:30+00:00", "released_at": "2026-08-10T15:05:44+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.14/argus-wordpress-defence-7.23.14.zip", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.19/argus-wordpress-defence-7.23.19.zip",
"sha256": "6b2365b173bd8e583a5d04021d205c773f927217b4870fc3ebff8c298c53367b", "sha256": "b9b3b0530c9b2143101f6507918587b4ce0646ab7867b2488493addc9887200c",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": true, "critical": false,
"summary": "* Fixed a serious bug: the Firewall could block ordinary visitors just for arriving from an\n everyday link -- for example, a link shared on Facebook, whose own redirect URL happened to\n match a pattern the Firewall treated as suspicious. The underlying cause was broader than that\n one case: 132 of the Firewall's 137 protection rules were checking a visitor's Referer,\n User-Agent, and X-Forwarded-For information -- values a visitor doesn't control -- when they\n should only ever have been checking what a visitor actually submits (search terms, form fields,\n comments, and similar). Those three values are now excluded everywhere except the handful of\n rules that specifically need them (Log4Shell-style attacks are delivered through exactly those\n values, so detection there is unchanged). No settings change needed; this takes effect\n automatically.", "summary": "* Hardened the optional page cache: cached pages can no longer be reached directly as raw files --\n every request still goes through ARGUS's normal security checks, including an active IP block,\n before anything is served.\n* Fixed a rare timing issue where, under heavy simultaneous traffic to the same page right as its\n cache was refreshing, a visitor could in theory receive an incomplete page. Cache updates are now\n published in a single, all-or-nothing step.",
"signature": "l3gHdqDlNbkuk88XuJpVOMiAbAMNVoht7lVJ0UgkgvcLgDUTmcnaYS9g6XoHqH6sPTkmLA6TL2SYe3d2d1NOCA==" "signature": "3O5e3JSEe/mKeN9zMCNS2d2KXgeUsf1B+ffzTZV7giVv4j9cyNcWm9tEy2YwgMJuyeSh2LlSix8MPF1AXABVCQ=="
} }