Live data from Hacker News

Password leaks bigger than first thought

h-online.com

51–55 of 55 posts

Re: Password leaks bigger than first thought

#51

Earlier quoted context omitted.

They usually use less than one bit per password.

People here don't know what rainbow tables are. If you asked them to build a rainbow table, you'd get... a table. (You're right.)

Thank you for the contentless comment. Instead, you might consider offering a more interesting algorithm, its tradeoffs, and why it is beneficial to take more computation time?

Re: Password leaks bigger than first thought

#52
post #10

Earlier quoted context omitted.

Microsoft Active Directory servers store passwords as plain MD4 hashes. http://16s.us/ms_ad_hashes/ These servers are used by governments and large organizations all over the world.

I would like to assume that the REALLY big companies like Google, Microsoft, Apple, Amazon, etc. can figure out how to effectively store passwords. While I acknowlege that Active directory is a bit different from a web service, if this can't be realized, god knows what's happening with the other 500 sites we all have accounts on (that invariably use shared passwords: http://xkcd.com/792/ ). I really love it when I ge…

Discussing hashes internally with Commander Adams, among the reasons we use unsalted hashes for internal passwords was that Google Mail for Domains (with which we use an SSO tool) doesn't work with salted hashes.

Or should I be siccing Krell monsters on the good Commander again?

Re: Password leaks bigger than first thought

#53
post #16

What do people think about outsourcing your authentication to someone else? Full Disclosure: I'm currently working on a brandable authentication host ( http://www.authic.com ) that will outsource the pain of storing your password hashes securly and provide your web app with slick a user account UX.

My own personal attitude is that I'd prefer having independent, unlinked accounts among various service providers, for which I use long, randomly generated passwords.

My risk from any given service is relatively low. My passwords are strong enough (trillions to quintillions of years brute-forcing time per the online calculator's I've checked -- with similarly constructed passwords, not my actual ones, natch) that risk of bruting a hashed key is low, and I don't re-use passwords. For services that store passwords in cleartext (still fairly common practice on mailing lists), no big loss either.

Re: Password leaks bigger than first thought

#54
post #51

Earlier quoted context omitted.

People here don't know what rainbow tables are. If you asked them to build a rainbow table, you'd get... a table. (You're right.)

Thank you for the contentless comment. Instead, you might consider offering a more interesting algorithm, its tradeoffs, and why it is beneficial to take more computation time?

A rainbow table doesn't store every hash for the password space it's built for. I'm sure you already knew that, but decided to pretend otherwise when calculating the size of one.

Re: Password leaks bigger than first thought

#55
post #6

"And one amusing detail – although eHarmony implores its users to use strong passwords including both upper and lower case letters, it saves the passwords in all upper case" This is truly beautiful - made my day :)

Brilliant. Possibly even more stupid than making people use E-mail addresses as user IDs. Do they do that too? Apple, Facebook, and LinkedIn make this blunder: http://goldmanosi.blogspot.com/2012/06/forcing-people-to-use...
Post reply on HN