>It does introduce the danger of algorithmic complexity attacks
>if .* is used instead of .{0,20} though -- but we may be able to help
>this if we spot that kind of thing in --lint.

I still don't understand why .* is more dangerous in rawbody rules than it is 
in full rules.  Any cases where it would have shown up in rawbody, it currently 
exists in a full rule.  Of course, hopefully those are few and far between.

BTW, if .* were the only concern, it would be moderately trivial to enhance 
rule syntax checking to disallow that pattern.

             Loren

Reply via email to