Use v3/dev/performance of ModSecurity because of performance
issues when combined with the owasp CRS See: https://github.com/SpiderLabs/ModSecurity/issues/1641
This commit is contained in:
parent
d1ae7ff29c
commit
41a0e3026b
1 changed files with 2 additions and 2 deletions
|
@ -188,7 +188,7 @@ git submodule update
|
|||
|
||||
# build modsecurity library
|
||||
cd "$BUILD_PATH"
|
||||
git clone --depth 1 -b v3/master --single-branch https://github.com/SpiderLabs/ModSecurity
|
||||
git clone --depth 1 -b v3/dev/performance --single-branch https://github.com/SpiderLabs/ModSecurity
|
||||
cd ModSecurity/
|
||||
git submodule init
|
||||
git submodule update
|
||||
|
@ -338,7 +338,7 @@ cd ..
|
|||
# Download modsecurity.conf
|
||||
mkdir modsecurity
|
||||
cd modsecurity
|
||||
curl -sSL -o modsecurity.conf https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v3/master/modsecurity.conf-recommended
|
||||
curl -sSL -o modsecurity.conf https://raw.githubusercontent.com/SpiderLabs/ModSecurity/v3/dev/performance/modsecurity.conf-recommended
|
||||
|
||||
# OWASP CRS v3 rules
|
||||
echo "
|
||||
|
|
Loading…
Reference in a new issue