News for hackers. Stuff that matters.
Re:The “Chad” bug by timberburn on Thursday December 31, 2015 @03:15AM (#10816787)
When I was setting up an account on Comcast's website, I was consistently getting an nondescript internal server error when submitting the form.

Took me quite awhile and many failed attempts to find that Comcast will throw an error when your requested username contains "comcast".

Re:The “Chad” bug by josegonzalez on Thursday December 31, 2015 @06:31AM (#10817201)
Same for ConEd.

Moneygram will freeze payments with the word "moneygram" in the associated email. Which is great for those of us that use catch-all emails and use the email address to discern what to do with an email...

Re:The “Chad” bug by rincebrain on Thursday December 31, 2015 @08:30AM (#10817472)
I've had a number of fun failure modes like that.

My current favorite two include when the change password form permitted longer passwords than the login page, and one where the change password form happily allowed special characters, but if there was e.g. a semicolon in the password, submitting it from the login page would throw a SQL error.

Re:The “Chad” bug by hidroto on Thursday December 31, 2015 @03:19AM (#10816799)
i wonder if that is to stop people from using names like comcastSucks or worse.
Re:The “Chad” bug by rdancer on Thursday December 31, 2015 @10:41AM (#10817993)
It may not have been the rationale, but it sure must be the most common use-case.
Re:The “Chad” bug by akurtzhs on Friday January 01, 2016 @10:54PM (#10824934)
It also avoids security problems with fraudsters creating official looking emails - "comcastsupport" and the like.