News for hackers. Stuff that matters.
Re:How *NOT* To Do A Password Field by Tloewald on Saturday April 12, 2014 @08:29AM (#7577667)
The problem with really awful password interfaces lies mainly with big institutions (banks!) who are unlikely to be influenced by bloggers linked on hacker news.

Ever since switching to a password manager (1Password in my case) I've become acutely aware of how many places have ridiculous restrictions on passwords (especially maximum lengths and character restrictions), and the worst offenders are invariably banks and financial sector sites.

Re:How *NOT* To Do A Password Field by chrismcb on Saturday April 12, 2014 @04:34PM (#7579084)
It seems like the more secure you need your data to be, the worse their password restrictions are. Restrictions such as no special characters, or an arbitrary short length raises a red flag. It says they don't really know what they are doing, and it makes me wonder what else is broken.
Re:How *NOT* To Do A Password Field by SimHacker on Saturday April 12, 2014 @06:15PM (#7579412)
And no SQL keywords allowed in passwords. Because they like to advertise that they don't bother escaping user input before concatenating sql strings to store plain text passwords in the database.

http://stackoverflow.com/questions/13738141/blacklist-filter...

Re:How *NOT* To Do A Password Field by krapp on Saturday April 12, 2014 @06:23PM (#7579433)
I'd bet that patterns like

    $db->execute("INSERT INTO USERACCOUNTS ('username','password') VALUES ('".$_POST['username']."','".$_POST['password']."')");
are more common than anyone wants to believe.
Re:How *NOT* To Do A Password Field by SimHacker on Saturday April 12, 2014 @06:38PM (#7579478)
The PHP manual pages are full of user comments with helpful suggestions just like that, which incompetent programmers copy and paste into production systems. But I think of it as a good thing, an instance of evolution in action, because banks that hire such stupid programmers deserve to have all their money stolen from them.
Re:How *NOT* To Do A Password Field by edent on Saturday April 12, 2014 @08:46AM (#7577702)
I just hope that one of their consultants' designers read my blog :-)
Re:How *NOT* To Do A Password Field by Tloewald on Saturday April 12, 2014 @04:48PM (#7579140)
We can hope :-)
Re:How *NOT* To Do A Password Field by NateDad on Saturday April 12, 2014 @08:34AM (#7577676)
The worst are the really random restrictions, like "can't have two of the same character next to each other" ...... what???