|
From: Breno S. P. (JIRA) <no...@mo...> - 2011-06-04 00:41:19
|
[ https://www.modsecurity.org/tracker/browse/MODSEC-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Breno Silva Pinto resolved MODSEC-172.
--------------------------------------
Resolution: Invalid Build
> Build - Integration Instructions broken. mod_security.c no longer exists.
> ----------------------------------------------------------------------------
>
> Key: MODSEC-172
> URL: https://www.modsecurity.org/tracker/browse/MODSEC-172
> Project: ModSecurity
> Issue Type: Bug
> Security Level: Normal
> Components: Documentation
> Environment: Centos 5.5 x64 Java 6.
> Reporter: BJ Chippindale
> Assignee: Breno Silva Pinto
>
> Instructions to build mod_security into Apache as a static module include copying mod_security.c into modules/proxy, running configure and the make.
> 1. mod_security.c does not exist.
> 2. Neither of modsecurity.c or mod_security2.c can be built in this fashion.
> Instructions to build as dso are similarly flawed.
> make install works, and as my Apache httpd is built as a threaded system, it installs the mod_security2.so into lib64/httpd/modules which is all good, but means that I have to roll-my-own instructions to create an apache rpm that contains this module, and cannot install it static at all.
> The pre-built rpm for mod_security requires liblua which is NOT installed on the target systems for the rpms.
> Since this is aimed at cautious sys-admin types, bad instructions are really extravagantly bad news.
> Thanks
> BJ Chippindale
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://www.modsecurity.org/tracker/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
