News for hackers. Stuff that matters.
Re:Some Problems Shouldn't Be Solved by saidajigumi on Tuesday March 31, 2015 @04:31PM (#9299679)
My own personal story of rage on this front: a site which, at the time I signed up, permitted arbitrary characters for its "security questions". I had the cheek to include characters other than pure alphanumerics.

Later, I return to this site and need to offer up the answers to the security questions. No problem... right up until I discover that some @$!#^%!!?! software developer put format guards on the security question answer fields at challenge time (vs. creation time). Yes, it was possible to create an answer to the (stupid) security questions which could not be answered by the website.

So now, my access to this site is literally sitting behind a several-months old developer ticket.

Re:Some Problems Shouldn't Be Solved by tchadwick on Tuesday March 31, 2015 @05:25PM (#9300011)
I created an account on justin.tv a long time ago and my username was 'grapefuckingjelly'. For awhile I couldn't log in because of a new validation on the log in form for swear words (the validation eventually went away). These days, I constantly hit a screen when logging into twitch.tv to transfer my justin.tv account over. It never seems to work... probably due to some validation.

I tried logging into twitch last night and it kept telling me my username/password are invalid, so I think my account is inaccessible again.

Re:Some Problems Shouldn't Be Solved by lurkinggrue on Wednesday April 01, 2015 @05:46PM (#9307159)
I tend to put a long 64 character hash as answers to the security questions. Have yet to experience that horrible bug.