From 5671a21a6f0c00b2ce68a8091b2a75ccca208996 Mon Sep 17 00:00:00 2001
From: martinhsv <55407942+martinhsv@users.noreply.github.com>
Date: Thu, 13 Jan 2022 17:11:43 -0500
Subject: [PATCH] Updated Reference Manual (v3.x) (mediawiki)
---
Reference-Manual-(v3.x).mediawiki | 61 ++-----------------------------
1 file changed, 3 insertions(+), 58 deletions(-)
diff --git a/Reference-Manual-(v3.x).mediawiki b/Reference-Manual-(v3.x).mediawiki
index 8854c5f..a3e98d1 100644
--- a/Reference-Manual-(v3.x).mediawiki
+++ b/Reference-Manual-(v3.x).mediawiki
@@ -533,68 +533,13 @@ ModSecurity hash engine will append, if specified, the user's session id or remo
== SecHashParam ==
-'''Description:''' Define the parameter name that will receive the MAC hash.
-
-'''Syntax:''' SecHashParam TEXT
-
-'''Example Usage:''' SecHashParam "hmac"
-
-'''Scope''': Any
-
-'''Version:''' 2.7.1-2.9.x
-
-'''Supported on libModSecurity:''' TBI
-
-ModSecurity hash engine will add a new parameter to protected HTML elements containing the MAC hash.
+'''Not supported in v3'''
== SecHashMethodRx ==
-'''Description:''' Configures what kind of HTML data the hash engine should sign based on regular expression.
-
-'''Syntax:''' SecHashMethodRx TYPE REGEX
-
-'''Example Usage''': SecHashMethodRx HashHref "product_info|list_product"
-
-'''Scope:''' Any
-
-'''Version:''' 2.7.1-2.9.x
-
-'''Supported on libModSecurity:''' TBI
-
-As a initial support is possible to protect HREF, FRAME, IFRAME and FORM ACTION html elements as well response Location header when http redirect code are sent.
-
-The possible values for TYPE are:
-*'''HashHref''': Used to sign href= html elements
-*'''HashFormAction''': Used to sign form action= html elements
-*'''HashIframeSrc''': Used to sign iframe src= html elements
-*'''HashframeSrc''': Used to sign frame src= html elements
-*'''HashLocation''': Used to sign Location response header
-
-; Note : This directive is used to sign the elements however user must use the @validateHash operator to enforce data integrity.
-
+'''Not supported in v3'''
== SecHashMethodPm ==
-'''Description:''' Configures what kind of HTML data the hash engine should sign based on string search algoritm.
-
-'''Syntax:''' SecHashMethodPm TYPE "string1 string2 string3..."
-
-'''Example Usage''': SecHashMethodPm HashHref "product_info list_product"
-
-'''Scope:''' Any
-
-'''Version:''' 2.7.1-2.9.x
-
-'''Supported on libModSecurity:''' TBI
-
-As a initial support is possible to protect HREF, FRAME, IFRAME and FORM ACTION html elements as well response Location header when http redirect code are sent.
-
-The possible values for TYPE are:
-*'''HashHref''': Used to sign href= html elements
-*'''HashFormAction''': Used to sign form action= html elements
-*'''HashIframeSrc''': Used to sign iframe src= html elements
-*'''HashframeSrc''': Used to sign frame src= html elements
-*'''HashLocation''': Used to sign Location response header
-
-; Note : This directive is used to sign the elements however user must use the @validateHash operator to enforce data integrity.
+'''Not supported in v3'''
== SecGeoLookupDb ==
'''Description''': Defines the path to the database that will be used for geolocation lookups.