Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using pbkdf2Sync function with sha256 gives different key with different system architecture (32 bit and 64 bit) #148

Open
GoogleCodeExporter opened this issue Jan 22, 2016 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.Create a simple javascript and require crypto.
2.crypto.pbkdf2Sync("12345", "salt", 10000, 14, "sha256");
3.Run it in with 32 bit and 64 bit systems.

What is the expected output? What do you see instead?
Both should return same output but its observed that outputs vary.

What version of the product are you using? On what operating system?
Using node v0.12.4 to run the script created in as mentioned above, tried on 
ubuntu 14.04 64 bit and 32 bit systems.

Original issue reported on code.google.com by [email protected] on 11 Jun 2015 at 2:15

@GoogleCodeExporter
Copy link
Author

Edit: Using Node v0.10.12 in 32 bit system and Node v0.12.4 in 64 bit system.

Original comment by [email protected] on 12 Jun 2015 at 5:33

@GoogleCodeExporter
Copy link
Author

The issue is with the implementation of node's crypto. Key output varies with 
node v0.10.12 and v0.12.4. 

Please disregard this issue. Apologies for bothering you.

Original comment by [email protected] on 12 Jun 2015 at 6:44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant