Re:Analysis of 32 million breached passwords
by Retric on Thursday January 21, 2010 @10:22AM
(#1067426)
It simplifies denial of service attacks, unless it's per IP, in which case a bonnet can try a few million passwords a day.
[ Parent
| on HN ]
Re:Analysis of 32 million breached passwords
by ShabbyDoo on Thursday January 21, 2010 @10:28AM
(#1067440)
I was thinking about limiting the number of password attempts per time interval by user -- not the total number of attempts at any user's password per interval. Does that fix the DOS concern?
In the RockYou case, a botnet could try 32M * # allowed/day given that it had a user list.
Re:Analysis of 32 million breached passwords
by Retric on Thursday January 21, 2010 @10:37AM
(#1067463)
With a large user list, some people will have really terrible passwords. So my guess would be by trying random week passwords to random accounts you could compromise a few hundred accounts in the first day. With diminishing returns over time.
Re:Analysis of 32 million breached passwords
by roundsquare on Thursday January 21, 2010 @11:06AM
(#1067528)
Even if it doesn't solve the problem, seems like it would help. In this case, a user would need to have a "very weak" password to be compromised. "Somewhat weak" passwords would be fine.
Also, after 100 or so attempts to login, I would thinking locking the user out would be fine (at least in many systems).
Re:Analysis of 32 million breached passwords
by Retric on Thursday January 21, 2010 @01:20PM
(#1067911)
That recreates the ability to lock people out of the system once you know their user ID.
Edit: However, a useful option is to force people to use a captia after a few bad atempts.
Re:Analysis of 32 million breached passwords
by ShabbyDoo on Thursday January 21, 2010 @10:44AM
(#1067483)
So, the user list would have to be available/harvestable? I guess this is an argument for having separate login Ids and published usernames. So, one couldn't just spider a site to create a user list.