david wrote:
The Perl book (I think it's the Programming Perl) has an example where a
certain reg. exp and string combination can make Perl's reg. engine run
forever (in terms of years!) because of backtracking. The solution the book
generally recommand is to use one of the newer reg. exp exten
David Garamond wrote:
> i'm creating a web interface for users to add their own mail filtering
> rules. the rules allow them to specify regexes to match headers and mail
> body. however, i'm a little concerned with how users can accidentally/
> intentionally use too complex regexes like this "(a+.
very interesting question... i can't wait to hear a solution myself if
anyone out there knows of one...
you might want to put the regex inside an "alarm/eval" block anyway so
that at least you can limit the maximum time it takes...
simran.
On Fri, 2002-11-29 at 13:48, David Garamond wrote:
>
i'm creating a web interface for users to add their own mail filtering
rules. the rules allow them to specify regexes to match headers and mail
body. however, i'm a little concerned with how users can accidentally/
intentionally use too complex regexes like this "(a+.*(b+.+(c*.+)*.*))*"
and the
