github_mirrors/ModSecurity
3
0
Fork 1
mirror of https://github.com/owasp-modsecurity/ModSecurity.git synced 2026-01-16 08:27:10 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated Reference Manual (v3.x) (mediawiki)

martinhsv
2022-01-13 15:35:54 -05:00
parent 652e0089c1
commit 0594e6a771
1 changed files with 2 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
Reference-Manual-(v3.x).mediawiki

@@ -1,6 +1,6 @@
= ModSecurity® Reference Manual = = ModSecurity® Reference Manual =
== Current as of v2.5.13 v2.6 v2.7 v2.8 v2.9 v3.0 == == Current as of v3.0.06 ==
=== Copyright © 2004-2018 [https://www.trustwave.com/ Trustwave Holdings, Inc.] === === Copyright © 2022 [https://www.trustwave.com/ Trustwave Holdings, Inc.] ===
= Table of Contents = = Table of Contents =
= Introduction = = Introduction =
@@ -44,24 +44,7 @@ ModSecurity is available under the Apache Software License v2 [http://www.apache
= Installation for Apache = = Installation for Apache =
== Prerequisites == == Prerequisites ==
=== ModSecurity 2.x works only with Apache 2.0.x or higher ===
The ModSecurity team works hard to ensure that ModSecurity version 2.x will work with all versions of Apache 2.x and higher. If you find incompatibilities on any version (2.2.x, 2.4.x, or 2.6.x) please immediately inform the ModSecurity team
=== mod_uniqueid ===
Make sure you have <code>mod_unique_id</code> installed.
mod_unique_id is packaged with Apache httpd.
=== libapr and libapr-util ===
libapr and libapr-util - http://apr.apache.org/
=== libpcre ===
http://www.pcre.org/
=== libxml2 ===
http://xmlsoft.org/downloads.html
=== liblua v5.x.x ===
This library is optional and only needed if you will be using the new Lua engine - http://www.lua.org/download.html
; Note : that ModSecurity requires the dynamic libraries. These are not built by default in the source distribution, so the binary distribution is recommended. ; Note : that ModSecurity requires the dynamic libraries. These are not built by default in the source distribution, so the binary distribution is recommended.
@@ -163,19 +146,7 @@ You should now have ModSecurity 2.x up and running.
#'''--enable-lua-cache''' - Enables lua vm caching that can improve lua script performance. Difference just appears if ModSecurity must run more than one script per transaction. #'''--enable-lua-cache''' - Enables lua vm caching that can improve lua script performance. Difference just appears if ModSecurity must run more than one script per transaction.
#'''--enable-request-early''' - On ModSecurity 2.6 phase one has been moved to phase 2 hook, if you want to play around it use this option. #'''--enable-request-early''' - On ModSecurity 2.6 phase one has been moved to phase 2 hook, if you want to play around it use this option.
#'''--enable-htaccess-config''' - It will allow the follow directives to be used into .htaccess files when AllowOverride Options is set : #'''--enable-htaccess-config''' - It will allow the follow directives to be used into .htaccess files when AllowOverride Options is set :
<pre>
- SecAction
- SecRule
- SecRuleRemoveByMsg
- SecRuleRemoveByTag
- SecRuleRemoveById
- SecRuleUpdateActionById
- SecRuleUpdateTargetById
- SecRuleUpdateTargetByTag
- SecRuleUpdateTargetByMsg
</pre>
= Installation for NGINX = = Installation for NGINX =
The extensibility model of the nginx server does not include dynamically loaded modules, thus ModSecurity must be compiled with the source code of the main server. Since nginx is available on multiple Unix-based platforms (and also on Windows), for now the recommended way of obtaining ModSecurity for nginx is compilation in the designated environment. The extensibility model of the nginx server does not include dynamically loaded modules, thus ModSecurity must be compiled with the source code of the main server. Since nginx is available on multiple Unix-based platforms (and also on Windows), for now the recommended way of obtaining ModSecurity for nginx is compilation in the designated environment.