Live data from Hacker News

Scribd hacked – emails and hashed passwords leaked

support.scribd.com

71–72 of 72 posts

Re: Scribd hacked – emails and hashed passwords leaked

#71

Earlier quoted context omitted.

Unique salts have to be stored somewhere. A common practice is to just use another piece of information associated with their account. The purpose of a salt is to make various bruteforcing attacks difficult. It doesn't do much if someone has full access to a system.

> Unique salts have to be stored somewhere. A common practice is to just use another piece of information associated with their account. The purpose of a salt is to make various bruteforcing attacks difficult. All absolutely true. > It doesn't do much if someone has full access to a system. Not true. Without salt they can try passwords and if the hash matches ANY in the system they know the password for those account…

The only real advantage you gain from a salt these days is that a precompiled database of hashes can't be used against you. Whether it be from someone's personal collection or one of those web-based hash sites.

Generating a rainbow table for each user isn't that much more difficult or time-consuming than having a single rainbow table. Processing power is cheap and easy to come by these days. A small botnet can be rented to generate rainbow tables at a faster rate than most supercomputers.

Re: Scribd hacked – emails and hashed passwords leaked

#72
post #32
post #24

Earlier quoted context omitted.

This seems to imply that many of (all?) the emails/encrypted passwords were leaked, but you don't consider most of them "compromised"...

I'd like to echo this concern -- were all emails/encrypted passwords leaked, but you only consider those protected by outdated hashing schemes to be compromised? If so, I feel you have an obligation to alert ALL of your users.

Additional question: when did users first alert you to the hack?
Post reply on HN