RE: [mod-security-users] Modsecurity Static Build

[Jeff T. <jt...@es...>]

I used the proxy folder because it seemed logical, since I was building
Apache to use as a reverse proxy, which of course is a great place to
add in mod_security. :-)=20

> -----Original Message-----
> From: Ivan Ristic [mailto:iv...@we...]=20
> Sent: Friday, September 09, 2005 12:46 PM
> To: Jeff Tharp
> Cc: mod...@li...; d.b...@ge...
> Subject: Re: [mod-security-users] Modsecurity Static Build
>=20
> Jeff Tharp wrote:
> > Not sure if this is the best way, but here's what I found works for
> > compiling mod_security in statically for Apache 2 (I was=20
> building Apache
> > 2.0.54 in this case):
> >=20
> >>Apache is custom compiled with ModSecurity statically=20
> >>linked.  To do this, I copied the mod_security.c file to the=20
> >>modules/proxy folder in the extracted source code for Apache,=20
> >>then added the following flags to configure (for Apache):
> >>	  --enable-security --with-module=3Dproxy:mod_security.c
>=20
>    Thanks for that Jeff,
>=20
>    I knew someone wrote about an easy way to compile mod_security
>    statically with Apache 2 but I couldn't find the email. By
>    placing mod_security into an existing module directory you
>    are taking advantage of the existing config.m4 and Makefile.in
>    files. Much better than what I did :)
>=20
> --=20
> Ivan Ristic
> Apache Security (O'Reilly) - http://www.apachesecurity.net
> Open source web application firewall - http://www.modsecurity.org
>=20