News for hackers. Stuff that matters.
Re:The FBI stole an Instapaper server in an unrelated raid by kragen on Thursday June 23, 2011 @05:44PM (#2690021)
To clarify, I assume you mean that using secure password hashes instead of insecure ones does not help users who use one-time effectively-random passwords, because those users are already safe?

That is true.

However, it seems to me that the combination of an effectively-random password and password hashing does protect users, because their password is not effectively crackable in a situation like this. Additionally, there's a tradeoff between how secure your password hashing is and how much randomness users need to put into their password: every additional factor of 1000 in the iterations of the hash saves you a random character or two.

Re:The FBI stole an Instapaper server in an unrelated raid by sunchild on Thursday June 23, 2011 @09:01PM (#2690546)
I wish everyone could use complex, unique, strong passwords all the time, but some use cases just don't support it. For example, I have to type my Apple ID into my iPhone/iPad what seems like every 5 minutes in iOS. Without access to 1password or a similar tool, I just can't use a strong password. Even if I did, I couldn't change it as often as I'd like to. FWIW, I wish I could.
Re:The FBI stole an Instapaper server in an unrelated raid by sliverstorm on Thursday June 23, 2011 @10:46PM (#2690756)
security vs. convenience
Re:The FBI stole an Instapaper server in an unrelated raid by sunchild on Friday June 24, 2011 @01:33AM (#2691140)
My point was that the choice is sometimes not left in the user's direct control. If I thought I could choose an absurdly strong password (e.g., to overcome the shortcomings of the developer's choice of SHA1), I would always do that – except if I'm going to need to enter that password from memory a bunch of times per day.