Update signed manifest to 7.41.0
This commit is contained in:
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.40.0",
|
||||
"released_at": "2026-09-17T10:42:49+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.40.0/argus-wordpress-defence-7.40.0.zip",
|
||||
"sha256": "9fc415ef804bfd2f584fbaeb69660a0ef963e52773d0c8913cd40d56a78ccd29",
|
||||
"version": "7.41.0",
|
||||
"released_at": "2026-09-17T11:36:03+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.41.0/argus-wordpress-defence-7.41.0.zip",
|
||||
"sha256": "311dacbd64a9604dba16de4329203899dd5a85aac0f0e78ea5670e2123069958",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* Security hardening: this site's IP-based protections (firewall, brute-force login protection,\n REST/API abuse protection, WooCommerce checkout guard, two-factor) now correctly recognise real\n visitor IP addresses when this site runs behind a reverse proxy, load balancer, or CDN, using the\n same trusted-proxy configuration already available under Form Protection. Previously, sites in\n that setup could see every visitor as the same address, weakening these protections.\n* Hardened the replay protection added in 7.39.0 further: it now remembers a short history of\n recently-applied WAD actions instead of only the single most recent one.",
|
||||
"signature": "n97VtOxZFjpDmUbFgbzjnf34nCcGUtGthdhs/oypEyEkidWgY6OiTt4WXUkz3ICEh5RJef9nfYxkyJeNaw1gBQ=="
|
||||
"summary": "* Findings now have a complete lifecycle: Resolve, Reopen, Accept Risk, False Positive/Suppress,\n Archive and Restore are all real, tracked actions (who did it, when, and why), available here in\n wp-admin and, if this site is connected to a WAD account, from there too -- WAD is never a\n separate copy of this data, every action there is carried out on this site the same way.\n* Contact Form 7's public feedback submission endpoint is now correctly recognised as an\n intentional, documented part of that plugin's own public API, the same way WooCommerce's Store\n API and Jetpack's public endpoints already were -- it no longer creates an unnecessary finding.",
|
||||
"signature": "ebCSGFVp8NzohM7F8+os2MaNT67iyaYxNaxeKSrj+utKUL3qF30VF7qy69wvyBicttrKvtlqcbzhl53QBlMRCQ=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user