Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
d89b0d09a9 | ||
|
|
fa1beeb71d | ||
|
|
68cc299d16 | ||
|
|
5657d78e13 | ||
|
|
0fb24b0e7b | ||
|
|
19957d44b0 | ||
|
|
4054510acc | ||
|
|
a0885f319a | ||
|
|
a8cdbef65a | ||
|
|
806094d6a0 | ||
|
|
0faf78287a | ||
|
|
235169e8ac | ||
|
|
67323f0204 | ||
|
|
f3a00c618b | ||
|
|
d39aa6f9bc | ||
|
|
efb0dfc838 | ||
|
|
7fa580d4d6 | ||
|
|
bd3275d252 |
+6
-6
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.42.0",
|
"version": "7.60.0",
|
||||||
"released_at": "2026-09-17T12:12:41+00:00",
|
"released_at": "2026-10-07T20:29:14+00:00",
|
||||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.42.0/argus-wordpress-defence-7.42.0.zip",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.60.0/argus-wordpress-defence-7.60.0.zip",
|
||||||
"sha256": "c7821aa239c9a50576e5b3fdf48547ec1e6f0817d656253d4bb85f46fd30dee7",
|
"sha256": "f42ceca31bdf8a4384a738769b7627ef336505705e27d0ae8fe66efb6a6a9b00",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": false,
|
||||||
"summary": "* If this site is connected to a WAD account, findings shown there now include ARGUS's full\n explanation -- what was found, why it matters, and what to check -- not just the recommended\n fix, so you no longer need to open wp-admin to see the complete picture.",
|
"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.",
|
||||||
"signature": "mUeeUqBfwGLpPNBmxtOFy1sLueaBn6Tj/61DYBcOAKoxVvdfIlFQUDSxHyTPgZDGiiy8NVhHJ370znBNkW3EBA=="
|
"signature": "pbBCsaPJoswbsr45WM2NaWbvPIACHVffHxCm/FC9DYWml9MpGB1zRvIrpCUFhal0J+BRTxjJ4nh/lPY+bTc6AA=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user