Re:BitInstant hacked: What and how it happened
by doublec on Saturday March 09, 2013 @10:39PM
(#5350601)
Maybe Site5 should ask better security questions then. If they want users to enter what is effectively a password for "Mother's maiden name" they should just ask for a security password.
[ Parent
| on HN ]
Re:BitInstant hacked: What and how it happened
by miles on Sunday March 10, 2013 @01:39AM
(#5350982)
Maybe Site5 should ask better security questions then.
Looks like they have allowed users to create their own for quite a while:
We have allowed customers to write their own security questions for over two and a half years now.
http://www.site5.com/blog/s5/security-and-social-engineering...
Re:BitInstant hacked: What and how it happened
by obstacle1 on Sunday March 10, 2013 @12:24AM
(#5350847)
I agree that the true-to-life reminder questions are probably an outdated model. However there's nothing intrinsically wrong with the maiden name question. There is no server-side code checking in with your mother or running her middle name against a federal database, you can enter whatever you want in the box. Surely people who are savvy enough to be trading in Bitcoin realize this.
Re:BitInstant hacked: What and how it happened
by michaelt on Sunday March 10, 2013 @07:27AM
(#5351484)
However there's nothing intrinsically wrong with the
maiden name question.
Asking users to enter their mother's maiden name, when you actually think they certainly shouldn't do that, then blaming your customers for having used their maiden name, seems like an odd way of doing it.If mother's maiden name isn't a good enough security question, stop asking it! And we all know it isn't a good enough security question.
Re:BitInstant hacked: What and how it happened
by raverbashing on Sunday March 10, 2013 @04:07AM
(#5351137)
Yes
It's a pain, but I don't trust this "Mother's Maiden name" invention.
Problem is remembering this (and some offline systems have it as well, oh well)
So if you think I'm going to put the actual name there you're wrong. Maybe not +@sfghh#54$=24 but something different.