mod_security

[NC-Designs]

Originally Posted by mistwang

Those rules should work fine with 4.1 release.
We need to either check it on your server, or copy your configuration to our lab environment to reproduce it.

I have PMed you my email, please could you get back to me on that address so I can provide you with a login so you could take a look?

Regards,
Chris

[sux0r]

I get these errors with the latest gotr00t rule set which i tried.

20_asl_useragents.conf
00_asl_rbl.conf
10_asl_rules.conf



o.O

[NC-Designs]

Originally Posted by sux0r

I get these errors with the latest gotr00t rule set which i tried.

20_asl_useragents.conf
00_asl_rbl.conf
10_asl_rules.conf

o.O

Yeah I get the Location match authType errors that you are getting.

[NiteWave]

please confirm if it's the latest 4.1?
Last-Modified: Tue, 03 May 2011

[NC-Designs]

Originally Posted by NiteWave

please confirm if it's the latest 4.1?
Last-Modified: Tue, 03 May 2011

Yep Tuesday 3rd May. Just a quick screenie of the errors im getting too -

[sux0r]

Even with the First 4.1 build im getting the errors.
I didnt bother much about it.

[mistwang]

The <LocationMatch> issue should be addressed in our 4.1.1 release when you put security rule in native LSWS configuration.

However, for vhost configured through httpd.conf, you should configure mod_security through httpd.conf as if Apache is used.

[sux0r]

Configured ModSec from httpd.conf
And the <LocationMatch> errors disappeared.

These are the errors now whichs regarding 10_asl_rules.conf
From GotRoot Rule set.

[optize]

No update?

[chernann]

I signed up for a gotroot subscription and tried the rules as suggested for a cpanel installation, i.e. a relatively light rule set.

While most rules parsed ok, performance on the server was significantly degraded, a normal dynamic page that delivered in 300 milliseconds would take 20 seconds to load. It looks like the mod security implementation needs to be optimized or precompiled in some way, or an apache reverse proxy run in front of litespeed.