You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
Details of the problem can be found in this stackoverflow.com question:
http://stackoverflow.com/questions/11268307/should-all-implementations-of-pbkdf2
-generate-the-the-same-key-from-identical-in
What is the expected output? What do you see instead?
CryptoJS's pbkdf2 output should match that of Node.js crypto.pbkdf2.
What version of the product are you using? On what operating system?
CryptoJS v3.0.2 on Windows 7 x64
Original issue reported on code.google.com by da...@vervestudios.co on 29 Jun 2012 at 8:59
The text was updated successfully, but these errors were encountered:
You'll have to fill me in on some details of NodeJS to diagnose the issue.
How does NodeJS convert strings to bits? Latin1? UTF-8?
Does NodeJS have you specify the key length in bits, bytes, or words?
What does your generateSalt function return?
Original comment by Jeff.Mott.OR on 29 Jun 2012 at 9:18
Looks like I figured it out.
In the rolled up PBKDF2.js script in "CryptoJS v3.0.2.zip"
`CryptoJS.enc.Base64` is `undefined`; this was probably intended, but not
something I noticed.
I was comparing node's Base64 encoded output to CryptoJS's hex output.
Another caveat was that the keySizes aren't compatible between CryptoJS and
node.js. Node needs `keySize * 4` in order to output an identical key. I'm not
familiar with what's going on under the hood in either case; but I'll just
assume that's intended.
Node.js's PBKDF2's documentation is pretty scarce; it does, however, say its
"key" parameter is named `keylen`.
FYI: Node.js's crypto library is just a wrapper around some OpenSSL functions.
Original comment by da...@vervestudios.co on 29 Jun 2012 at 9:36
Original issue reported on code.google.com by
da...@vervestudios.co
on 29 Jun 2012 at 8:59The text was updated successfully, but these errors were encountered: