github_mirrors/ModSecurity
3
0
Fork 1
mirror of https://github.com/owasp-modsecurity/ModSecurity.git synced 2025-09-29 11:16:33 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merged in 2.5.x changes into trunk.

Browse Source
This commit is contained in:
b1v1r
2010-02-14 22:46:42 +00:00
parent f925a978ab
commit b784acd316
6 changed files with 714 additions and 257 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
doc/modsecurity2-apache-reference.xml
View File

@@ -460,18 +460,29 @@ SecAuditLogStorageDir logs/audit
<para><emphasis>Processing Phase:</emphasis> N/A</para>
<para><emphasis>Scope:</emphasis> Any</para>
<para><emphasis>Version:</emphasis> 2.0.0</para>
<para><emphasis>Dependencies/Notes:</emphasis> This file is open on startup when the server
typically still runs as<emphasis> root</emphasis>. You should not allow non-root users to
have write privileges for this file or for the directory it is stored in..</para>
<para>This file will be used to store the audit log entries if serial audit logging format is
used. If concurrent audit logging format is used this file will be used as an index, and
contain a record of all audit log files created. If you are planning to use Concurrent audit
logging and sending your audit log data off to a remote Console host or commercial
ModSecurity Management Appliance, then you will need to configure and use the ModSecurity
Log Collector (mlogc) and use the following format for the audit log:</para>
<para>
<programlisting format="linespecific">SecAuditLog "|/path/to/mlogc /path/to/mlogc.conf"</programlisting>
</para>
<para><emphasis>Dependencies/Notes:</emphasis> This file is open on
startup when the server typically still runs as<emphasis>
root</emphasis>. You should not allow non-root users to have write
privileges for this file or for the directory it is stored in..</para>
<para>This file will be used to store the audit log entries if serial
audit logging format is used. If concurrent audit logging format is used
this file will be used as an index, and contain a record of all audit
log files created. If you are planning to use Concurrent audit logging
and sending your audit log data off to a remote Console host or
commercial ModSecurity Management Appliance, then you will need to
configure and use the ModSecurity Log Collector (mlogc) and use the
following format for the audit log:</para>
<note>
<para>Prior to 2.5.13 you may have been able to use a relative path to
a piped logger command, but this was broken on some platforms and the
feature was removed in 2.5.13 to make the platforms more
consitent.</para>
</note>
<para><programlisting format="linespecific">SecAuditLog "|/path/to/mlogc /path/to/mlogc.conf"</programlisting></para>
</section>
<section>
<title><literal>SecAuditLog2</literal></title>