3 ms·
I ported scrypt to Go (https://code.google.com/p/go/source/browse/scrypt/scrypt.go?repo=crypto https://code.google.com/p/go/source/browse/scrypt/scrypt.go?...),
by dchest 14y ago
I ported scrypt to Go (https://code.google.com/p/go/source/browse/scrypt/scrypt.go?repo=crypto https://code.google.com/p/go/source/browse/scrypt/scrypt.go?...), so I know how to store passwords ;-)
This has nothing to do with passwords. You can read about brokenness of RC4, MD5, or SHA1 in their respective Wikipedia articles.
- carbocation 14y agoFirst, thanks for your contribution. Second, I didn't downvote you. Third, the question was never whether you knew how to store a password. There are many reasons to need to be able to use even 'broken' primitives (esp. for compatibility with legacy apps or conversion), which makes them valuable (or at least necessary) for some apps. This is why I was guessing that your post was focused on passwords.
- dchest 14y agoI understand. I also said that there's no reason to use them for _new_ systems. BTW, suggested reading: http://cr.yp.to/talks.html#2013.03.12 http://cr.yp.to/talks.html#2013.03.12 ("Failures of secret-key cryptography").
- carbocation 14y agoGulp. You did; I missed it! My apologies. And thanks for that link. Slide 313 is terrifying.