Skip to content

Geoiplookup unable to lock proc mutex for non-httpd users #426

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.

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

Closed
rcbarnett-zz opened this issue Oct 17, 2013 · 3 comments
Closed

Geoiplookup unable to lock proc mutex for non-httpd users #426

rcbarnett-zz opened this issue Oct 17, 2013 · 3 comments
Assignees
Milestone

Comments

@rcbarnett-zz
Copy link
Contributor

MODSEC-278: When using ModSecurity with a per-user request handling module such as MPM-ITK or mod_ruid2, geoiplookup will not be able to lock the proc mutex and thus fail to do the lookup:

Message: Geo Lookup: Failed to lock proc mutex: Permission denied

Vhosts/directories that do not have a specific user assigned, but rather the 'global' httpd user, do not get this error message.

@rcbarnett-zz
Copy link
Contributor Author

Original reporter: lb06

@rcbarnett-zz
Copy link
Contributor Author

lb06: FYI: A workaround is possible using libapache2-mod-geoip. This module populates the ENV variables with GEO* data. You can then perform GEO lookups using SecRule ENV:GEOIP_* rather than with GEO:*.

@victorhora
Copy link
Contributor

The global mutex is optional since 112ba45 (included in 2.9.2 release)

This shouldn't be a concern with libModSecurity (aka 3.0) and libMaxMind.

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants