3 ms·
I really don't want to use this word, but this is retarded. Something like RFC 2898 would be a good starting point for explaining why. http://www.ietf.org/rfc/r
by huhtenberg 17y ago
I really don't want to use this word, but this is retarded. Something like RFC 2898 would be a good starting point for explaining why. http://www.ietf.org/rfc/rfc2898.txt http://www.ietf.org/rfc/rfc2898.txt
- codahale 17y agoI'm guessing you haven't read Provos and Mazières' USENIX paper. In the design considerations, they say: In general, a password algorithm, whatever its cost, should execute with near optimal efficiency in any setting in which it sees legitimate use, while offering little opportunity for speedup in other contexts. PBKDF1 and PBKDF2 both rely upon general-purpose hash functions, which are much faster in dedicated computing environments such as FPGA or GPU clusters. The Eksblowfish algorithm at the heart of bcrypt is extremely resistent to optimization. This is crucial for password storage, since if a CUDA implementation is 3-4 orders of magnitude faster than the implementation your application uses, you've just chipped off a huge chunk of the advantage offered by your hash function.
- tptacek 17y agoWhat a bizarre comment. PBKDFn and bcrypt are two very similar approaches to the same problem. If you're married to PKCS/IETF standards, go ahead and use PBKDF2. You're still essentially following the advice of this blog post.