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
This doesn't effect the verify() methods since they use the encoded hash.
But the hash() method creates a totally different hex hash and encoded string each time it's invoked even if a salt is provided..
Conversely, the hashRaw() function DOES return the same correct hash, using the provided salt, each time it's invoked.
Is this by design, or simple oversight?
My thoughts were that if a salt is provided, it should use it as a parameter in Argon regardless of whether or not you're generating an encoded pw hash output or just the hex value...
Please correct me if I'm wrong and it's working as intended.
Thanks!
The text was updated successfully, but these errors were encountered:
As the title says
The hash function uses a randomly generated salt on every invocation.
Wheres the hashRaw function takes into account the provided hash.
This doesn't effect the verify() methods since they use the encoded hash.
But the hash() method creates a totally different hex hash and encoded string each time it's invoked even if a salt is provided..
Conversely, the hashRaw() function DOES return the same correct hash, using the provided salt, each time it's invoked.
Is this by design, or simple oversight?
My thoughts were that if a salt is provided, it should use it as a parameter in Argon regardless of whether or not you're generating an encoded pw hash output or just the hex value...
Please correct me if I'm wrong and it's working as intended.
Thanks!
The text was updated successfully, but these errors were encountered: