News for hackers. Stuff that matters.
Re:Security Checklist by msbarnett on Sunday March 20, 2016 @02:33PM (#11324024)
> Are all form fields (with the exception of password fields) validated with a restrictive regex?

Please, whatever you do, do not try to regex validate people's names. A friend couldn't complete an order on a site the other day because it was rejecting his name as "invalid" per its shitty regex.

See also Falsehoods Programmers Believe About Names[1]

[1] http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b...

Re:Security Checklist by DrScump on Sunday March 20, 2016 @08:01PM (#11325325)
<do not try to regex validate people's names>

Or email addresses, without knowing all the legal characters. (An annoying percentage reject '+', which is a great Gmail tool for spotting how your email address "leaks out".)

Re:Security Checklist by NickNameNick on Sunday March 20, 2016 @11:30PM (#11326041)
And a huge number don't suport email addresses with 'bare' tld's.

see rfc 7085 "Top-Level Domains That Are Already Dotless"

https://webcache.googleusercontent.com/search?q=cache:rySaMA...

Re:Security Checklist by breakingcups on Monday March 21, 2016 @05:38AM (#11326996)
I thought those weren't allowed / encouraged by either ICANN nor IAB? They have a real-world possibility of colliding with internal hostnames.
Re:Security Checklist by beejiu on Sunday March 20, 2016 @03:36PM (#11324294)
In addition, a poorly written Regex can open you up to a Regular Expression DOS attack. If anything, it should be on the security checklist as something not to do.
Re:Security Checklist by __john on Sunday March 20, 2016 @07:07PM (#11325147)
A friend and I made this for fun. It is a joke and only here for entertainment value, don't put it in production. https://github.com/JonZudell/Genetic_Expression