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
Using the util.pwHash helper function I run in to some issues when hashing passwords. If the memlimit is set to sensitive it sometimes crashes with this error:
Uncaught (in promise) Error: invalid usage
at b (libsodium-wrappers.js:1)
at Object.Te [as crypto_pwhash] (libsodium-wrappers.js:1)
at util.js:108
at <anonymous>
This is repeatable in the Chrome test browser I am using for Cypress integration tests but it appears to work fine in Firefox and regular Chrome.
Setting the memlimit to crypto_pwhash_MEMLIMIT_INTERACTIVE as suggested here allows it to work correctly in the chrome test browser. Not sure what the ramifications of this are...
As an aside, the hashing is MUCH faster when the memlimit is set to interactive. It is very slow (~3-4 seconds) using the original configuration.
The text was updated successfully, but these errors were encountered:
willemolding
changed the title
sodium.crypto_pwhash_MEMLIMIT causes error when set to SENSITIVE
In pwHash, sodium.crypto_pwhash_MEMLIMIT causes error when set to SENSITIVE
Feb 27, 2019
Using the util.pwHash helper function I run in to some issues when hashing passwords. If the memlimit is set to sensitive it sometimes crashes with this error:
This is repeatable in the Chrome test browser I am using for Cypress integration tests but it appears to work fine in Firefox and regular Chrome.
Setting the memlimit to
crypto_pwhash_MEMLIMIT_INTERACTIVE
as suggested here allows it to work correctly in the chrome test browser. Not sure what the ramifications of this are...As an aside, the hashing is MUCH faster when the memlimit is set to interactive. It is very slow (~3-4 seconds) using the original configuration.
The text was updated successfully, but these errors were encountered: