Skip to content

When configuring ModSecurity, make sure that not both legacy GeoIP an… #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 25, 2021
+4 −1
Merged

When configuring ModSecurity, make sure that not both legacy GeoIP an… #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -247,11 +247,14 @@ ARG MODSECURITY_VERSION
ARG MODSECURITY_DEB_VERSION
WORKDIR /usr/local/build

# make sure we include libmaxminddb so that modsecurity compiles with GeoLite2 support
# Make sure we include libmaxminddb so that modsecurity compiles with GeoLite2 support
COPY --from=libmaxminddb /usr/local/debs /usr/local/debs
RUN dpkg -i /usr/local/debs/*.deb
RUN rm -rf /usr/local/debs/*.deb

# Make sure to remove any traces of old GeoIP libraries, because if both legacy GeoIP and MaxMind libraries are present, you get this bug: https://github.com/SpiderLabs/ModSecurity/issues/2041
RUN apt-get purge -y libgeoip-dev

RUN current_state.sh before

# Required for modsecurity-nginx: https://www.nginx.com/blog/compiling-and-installing-modsecurity-for-open-source-nginx/
Expand Down