Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
9f13bcabc4 | ||
|
|
78dba72fad | ||
|
|
770acaf061 | ||
|
|
2ecef66d62 | ||
|
|
94e572214c | ||
|
|
da64bcaadb | ||
|
|
001bbefa3f | ||
|
|
ef6555a1e4 | ||
|
|
8832cee2da | ||
|
|
0c3ac9e463 | ||
|
|
22b7a76a6e | ||
|
|
1544198d02 | ||
|
|
4b3e877127 | ||
|
|
8324647177 | ||
|
|
eec9b0e6f0 | ||
|
|
301e39dc66 | ||
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda | ||
|
|
2ce45b9c2d | ||
|
|
21ed592b8b | ||
|
|
cc56098488 | ||
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 | ||
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 |
+6
-6
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.60.0",
|
"version": "7.84.0",
|
||||||
"released_at": "2026-10-07T20:29:14+00:00",
|
"released_at": "2026-11-03T16:46:14+00:00",
|
||||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.60.0/argus-wordpress-defence-7.60.0.zip",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.84.0/argus-wordpress-defence-7.84.0.zip",
|
||||||
"sha256": "f42ceca31bdf8a4384a738769b7627ef336505705e27d0ae8fe66efb6a6a9b00",
|
"sha256": "f8d9db1d4bd7b34955d96183aec8822024ea6a013fe53d63f4235a6db777190d",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": false,
|
||||||
"summary": "* Bot Protection: added Bot Signature Exceptions, so you can review a bot classification once and\n have that decision apply to every future request matching it -- not just one finding. Previously,\n dismissing a single Bot Filter finding never stopped the same signature from being flagged (and\n re-blocked) again on the next hit.\n* Bot Filter findings now have a \"Review Bot Classification\" action that opens Bot Protection with\n the signature already filled in, instead of making you hunt for the right settings page.\n* An exception can optionally be scoped to a specific IP range as well as the User-Agent, for a\n real, publicly-documented crawler (for example Google's own crawl ranges) -- recommended over a\n User-Agent-only exception, since a User-Agent header can be sent by anyone.",
|
"summary": "* Performance: the firewall now caches transform pipeline results within each request scan, eliminating redundant work when multiple rules share the same transforms. High-traffic sites will see reduced per-request CPU cost.\n* False positive fix: the PHP2Shell detection rules no longer flag saves from the built-in WordPress theme and plugin file editors. A logged-in user with the `edit_themes` or `edit_plugins` capability editing files through those screens will no longer be incorrectly blocked or banned.\n* Bot protection: site-clone and offline-download tools (htclone, SiteSucker, Teleport Pro, WebZip, Offline Explorer, Cyotek, WebStripper and others) are now detected and blocked at the HTTP level before they can scrape or copy site content.",
|
||||||
"signature": "pbBCsaPJoswbsr45WM2NaWbvPIACHVffHxCm/FC9DYWml9MpGB1zRvIrpCUFhal0J+BRTxjJ4nh/lPY+bTc6AA=="
|
"signature": "tyhCxYy0kblpHwusx7vigIe9MDjAnm1wjbT4G1Q3JvosYmX2vpbeo6Rrbq/GU+pJ4TxHSo0iIbnGigRg/eVZCg=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user