|
From: Ivan R. <iv...@we...> - 2006-02-01 14:07:17
|
CASTELLE Thomas wrote: > Well, I looked quickly on the Internet and it seems that it could happen > with IE-specific websites : > http://msdn.microsoft.com/library/default.asp?url=/workshop/author/dhtml/reference/events.asp Yes, but that would already be handled with onSelect[[:space:]]*= I don't think the second part =[[:space:]]*onSelect is needed. > Two other questions : > - Do you think you'll provide a simple tool to automatically download > new rulesets, compare them with the ones in production, detect changes > and integrate them in the production environment, like the > "rule-du-jour" script for spamassassin ? I don't have any immediate plans. It's like this: I can either choose to work on ModSecurity itself or on the related utilities. ModSecurity wins every time. I appreciate that it's not easy to start contributing to ModSecurity because of the complexities involved but it'd be really nice to see someone step up and work on the related utilities. (Also I am not sure there is a need for something like that because I don't see the generic rules changing often.) > - Do you know if a modsecurity log analysis tool exists ? One that could > generate a human-readable report daily with the different events > detected or blocked ? No, but I am working on a commercial tool for real-time log aggregation and reporting at the moment. A beta should be available in the next couple of weeks. -- Ivan Ristic, Technical Director Thinking Stone, http://www.thinkingstone.com Tel: +44 20 8141 2161, Fax: +44 87 0762 3934 |
