From 3e307848a4edc9f9d4213327813b731bf80d4aa9 Mon Sep 17 00:00:00 2001 From: b1v1r Date: Mon, 27 Jul 2009 22:26:25 +0000 Subject: [PATCH] Update docs to better cover build requirements and mention migration from 1.9 (MODSEC-33). --- doc/modsecurity2-apache-reference.xml | 54 +++++++++++++++++++++++---- 1 file changed, 47 insertions(+), 7 deletions(-) diff --git a/doc/modsecurity2-apache-reference.xml b/doc/modsecurity2-apache-reference.xml index 70bc4fa3..a894a49c 100644 --- a/doc/modsecurity2-apache-reference.xml +++ b/doc/modsecurity2-apache-reference.xml @@ -249,11 +249,12 @@
Installation - ModSecurity installation consists of the following steps: + ModSecurity installation requirements: - ModSecurity 2.x works with Apache 2.0.x or better. + ModSecurity 2.x works only with Apache 2.0.x or higher. Version + 2.2.x is highly recommended. @@ -264,17 +265,31 @@ - Install the latest version of libxml2, if it isn't already - installed on the server. + libapr and libapr-util + + http://apr.apache.org/ + + + + libpcre + + http://www.pcre.org/ + + + + libxml2 http://xmlsoft.org/downloads.html - Optionally install the latest version of Lua in the 5.1.x - branch, if it isn't already installed on the server and you will be - using the new Lua engine. + liblua v5.1.x + + This library is optional and only needed if you will be using + the new Lua engine. http://www.lua.org/download.html @@ -284,6 +299,21 @@ distribution is recommended. + + libcurl v7.15.1 or higher + + If you will be using the ModSecurity Log Collector (mlogc) to + send audit logs to a central repository, then you will also need the + curl library. + + http://curl.haxx.se/libcurl/ + + + + ModSecurity installation consists of the following steps: + + Stop Apache httpd @@ -444,6 +474,16 @@ LoadFile /usr/lib/liblua5.1.so moreinfo="none">WITH_PCRE_STUDY defined,which would possibly give you a slight performance edge in regular expression processing. + + Non-gcc compilers may have problems running out-of-the-box as the + current build system was designed around the gcc compiler and some + compiler/linker flags may differ. To use a non-gcc compiler you may need + some manual Makefile tweaks if issues cannot be solved by exporting + custom CFLAGS and CPPFLAGS environment variables. + + If you are upgrading from ModSecurity 1.x, please refer to the + migration matrix at http://www.modsecurity.org/documentation/ModSecurity-Migration-Matrix.pdf