LinkedIn passwords leaked

6.5 million password hashes posted on a Russian hacker site.

I don’t know how many times this is going to happen before the developers behind password storage get it.


Yes, it’s going to add a little bit to your development time, but it’s time well-spent.

When you don’t salt the hashes, it just takes one breach like this one to expose your user’s data.  When you have a list of 6.5 million passwords, how many of them are going to be found in a standard attacker’s dictionary?  Half?  More?

If the attacker has the email addresses linked to these passwords (there’s no proof of that yet), then there are probably 3 million valid combinations that have already been cracked.

And how many of those re-use that same password for Facebook, their banking, or for the email address itself?

You can’t rely on users to implement secure password practices for themselves.  So make sure that you follow best practices for storing the password that they entrust to you.

Add a random salt before hashing.




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s