Have same problem again...

ASL shows an update is available (in GUI), ran asl -u (which updated mod_sec rules OK) then yum update, returned no packages marked for update/osoletion.

So ran rpm -q asl, returned asl-1.9.7-1.el4.art (no duplicates this time).

Not sure why this happens every time on RHEL4/Plesk 8.3 for me? Any suggestions??

Thanks...

Same here, see also:
http://atomicrocketturtle.com/forum/vie ... highlight=

You're seeing the QA releases in the gui, nothing to worry about. It just means a big update is around the corner. If you want to play around with the QA builds you can activate the asl-2.0-testing repository in your /etc/yum.repos.d/asl.repo

Ok, so actualy we are updated only it does not look that way in de webGUI? And this will be gone after the update to 2.0?

OK, that make sense... a couple of further questions which may also be of relevance to others:

1. On a couple of occasions an ASL/mod_sec update has caused some major false-positives for our sites, is there a way to roll back to a previous mod_sec rule base until the (usually very quick) update/fix is forthcoming?
2. Having temporarily disabled a mod_sec sig to keep sites working correctly, is there a command to re-enable a sig and/or review any which are disabled?

Thanks

Very good question, I thought these updates are tested first before they are updated?

Yep they're tested before they go out. You just can't test for everything.

We do keep the old rules up on the updates server. You can always manually grab those and drop them off in the modsecurity.d dir.

I have been testing the new 1.9.8 ASL. Its really great. If you see the update for ASL, if you are keen you can install it and test for Scott (I always test the releases).

They are in the asl-2.0-testing channel

The new 1.9.8 uses the new clamav scanner all as part of ASL. Really good..

When can we expect stable ASL update?

We might wrap up on it today