Commit message (Collapse)AuthorAgeFilesLines
* www-apache/mod_security: remove oldMarek Szuba2020-11-091-108/+0
| | | | Signed-off-by: Marek Szuba <>
* www-apache/mod_security: update homepageAlexey Sokolov2020-06-041-3/+3
| | | | | | Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Alexey Sokolov <> Signed-off-by: David Seifert <>
* www-apache/mod_security: amd64 stable wrt bug #668050Mikle Kolyada2018-10-201-1/+1
| | | | | Signed-off-by: Mikle Kolyada <> Package-Manager: Portage-2.3.49, Repoman-2.3.11
* www-apache/mod_security: x86 stable (bug #668050)Thomas Deutschmann2018-10-141-2/+2
| | | | | Package-Manager: Portage-2.3.50, Repoman-2.3.11 Signed-off-by: Thomas Deutschmann <>
* www-apache/mod_security: new revision with updated default configuration.Michael Orlitzky2017-05-141-0/+108
I've made a few small changes to the configuration file that we install by default. First, I've added two settings, SecTmpDir and SecUploadDir, which serve a similar purpose as the existing SecDataDir. All of those need to be located somewhere safe, and the upstream defaults point to /tmp (which is not safe). It is therefore necessary that we override them, and point them to a location that is created and made private in the ebuild. We now use /var/lib/modsecurity/{data,tmp,upload} and I've made them mode 0750 by default (owned by apache:apache). I've also removed two settings that used to be present. Our default configuration is extremely close to the upstream defaults, and sets almost nothing in 79_mod_security.conf explicitly. The presence of SecHttpBlKey was therefore rather strange, since it was disabled by default and contained nothing Gentoo-specific. I've removed it for consistency (it is documented upstream for people who want it). The other setting that I've removed is SecGeoLookupDb. This one could at least be justified for containing a Gentoo-specific path. However, the path doesn't work out-of-the-box; it requires you to (manually, or via cron) update your GeoIP database at least once before using it. At that point, you know the location of the database, and can point mod_security to it yourself. Taking that into consideration, it again makes more sense to omit the setting for consistency and defer to the upstream documentation and defaults. Package-Manager: Portage-2.3.3, Repoman-2.3.1