deps - use ModSecurity v3.0.4 instead of v3.0.5 to avoid memory leak

This commit is contained in:
bunkerity 2021-08-25 17:12:38 +02:00
parent 0772a9ba8e
commit a056141609
No known key found for this signature in database
GPG Key ID: 3D80806F12602A7C
1 changed files with 4 additions and 1 deletions

View File

@ -459,7 +459,10 @@ CHANGE_DIR="/tmp/bunkerized-nginx/libmaxminddb-1.6.0" do_and_check_cmd make inst
# Download, compile and install ModSecurity
echo "[*] Clone SpiderLabs/ModSecurity"
git_secure_clone https://github.com/SpiderLabs/ModSecurity.git bf881a4eda343d37629e39ede5e28b70dc4067c0
# TODO : looks like memory leak is happening with ModSecurity 3.0.5
# so we keep 3.0.4 until a fixed version is available
#git_secure_clone https://github.com/SpiderLabs/ModSecurity.git bf881a4eda343d37629e39ede5e28b70dc4067c0
git_secure_clone https://github.com/SpiderLabs/ModSecurity.git 753145fbd1d6751a6b14fdd700921eb3cc3a1d35
echo "[*] Compile and install ModSecurity"
# temp fix : Debian run it twice
cd /tmp/bunkerized-nginx/ModSecurity && ./build.sh > /dev/null 2>&1