Test pathological regexes
Closed this issue · 4 comments
g3rv4 commented
Regexes that are bad bad bad probably break the system. Get some from @Mariano-SOes and test them!
mariano commented
I think you mean a different Mariano 🤷🏼♂️
…On Tue, 10 Apr 2018 at 08:58 Gervasio Marchand ***@***.***> wrote:
Regexes that are bad bad bad probably break the system. Get some from
@mariano <https://github.com/mariano> and test them!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABIpnzFIzBy0wyg3ydv__civsqKSgQWks5tnJ5kgaJpZM4TOHfm>
.
g3rv4 commented
yeah, sorry... I edited the comment but the email had already triggered... I imagine using GitHub with a cool handle has its disadvantages ;)
Mariano-SOes commented
Ckecklist:
- analize code
- Option Compiled?
- Explicit Capture
- Default to IgnoreCase and Singleline?
Meaning a user should use(?-i)
or(?-s)
to turn it off - Limit?
- Check culture info for
\w
& friends in Russian and Japanese - Identify problematic strings in db
- Tests
- Syntax errors
- Unicode properties
- Catastrophic backtracking
- Stack overflow / too many named groups
- Evil variable length lookbehings
- Regex-fu with balancing groups and conditionals
g3rv4 commented
I don't think we'll ever do this. Closing it to avoid noise on the list of issues.
Also, Mariano: hi! <3