Update signed manifest to 7.23.17

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.14",
-    "released_at": "2026-08-10T10:42:30+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",
-    "sha256": "6b2365b173bd8e583a5d04021d205c773f927217b4870fc3ebff8c298c53367b",
+    "version": "7.23.17",
+    "released_at": "2026-08-10T11:36:11+00:00",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.17/argus-wordpress-defence-7.23.17.zip",
+    "sha256": "2a5c55fca141a65574818ba553657f26486d3153d159c17a8a9a0182d2ac2621",
     "min_php": "7.4",
     "min_wp": "6.0",
-    "critical": true,
-    "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.",
-    "signature": "l3gHdqDlNbkuk88XuJpVOMiAbAMNVoht7lVJ0UgkgvcLgDUTmcnaYS9g6XoHqH6sPTkmLA6TL2SYe3d2d1NOCA=="
+    "critical": false,
+    "summary": "* Reduced false-positive security findings for recognized WordPress and WooCommerce functionality\n  -- normal, expected WooCommerce cart/storefront activity no longer shows up as a security issue\n  requiring your attention.\n* Findings you resolve or accept no longer reappear on their own within the hour.\n* Added a new \"Automatically Handled\" section on the Findings page, showing what ARGUS verified\n  and handled on its own -- separate from anything you decided yourself.\n* Replaced \"Delete\" with \"Archive\" for findings -- your security history is kept, not destroyed,\n  when you clear something from your queue.\n* Findings actions (Acknowledge, Resolve, Accept Risk, Archive) now show a short explanation of\n  what each one actually means.\n* The Security Score and Findings counts on the dashboard no longer count routine technical\n  inventory as active security issues.\n* An ARGUS Defence update verified through its own signed update process is no longer shown as a\n  file-integrity warning.",
+    "signature": "gbC2tegHF/ACYCy+w3apuZxJIcpNyxl2YmNsJUqI95iZD7PYzXC4X+uApNElf9+wzgStXFdEtEBnmIYvrXGxCQ=="
 }