![]() ![]() I believe what they do is the following:Ģ. I can't recall it off the top of my head, but Facebook has a similarly impressive system with more secret sauce involved for performance at scale. It's a good system, especially compared with the current best practice of simply hashing passwords with bcrypt and calling it a day. But as an extra measure symmetric encryption has already proven itself to be useful. Plus you can see your user's plaintext passwords (since you have the key), which you should not be able to do. If the password leaks, you expose all passwords in mere seconds. I certainly wouldn't rely on symmetric encryption alone to store passwords. Compare that to something like LinkedIn (SHA1) where enthusiasts have cracked almost 97% of the passwords in that leak. I'm betting their key was a full 168 bit random value that was immediately deleted when the leak came to light, so it's likely that value will never exist again in this universe. ![]() So, most of the passwords were never discovered. Other than the giant crossword puzzle created by the password hints combined with their choice of ECB mode to encrypt the passwords that allowed people to infer blocks of passwords, I haven't been able to find any evidence that the encryption key was leaked or guessed. Proof that they're not pointless: The adobe password leak.
0 Comments
Leave a Reply. |