I know it's common to see apache modules named mod_xxx, but modsecurity isn't called mod_security. Their webpage, their tarballs and all references to it around the web are "modsecurity". Calling it mod_security only makes it hard for people to find it/find references to it (such as on here). I suspect the installed module name is only called mod_security to look prettier in the config files with the other modules, but I'm only guessing. Is there a good reason to not rename it to modsecurity? Reproducible: Always Steps to Reproduce:
(In reply to comment #0) > Is there a good reason to not rename it to modsecurity? Yes, a lot of work for zero gain...
Are you ignoring the points I put accross, or don't you think any of them are valid?
Thanks for the bug report. If we move the module from the net-www/ category into www-apache/, that'll be the opportunity for us to rename the package. We'll take another look at this when/if we move the package. Best regards, Stu