Closed gpalomar closed 7 years ago
Hi, I don't really support PNaCl, it's provided as a reference, to compare the performance. Feel free to modify and adopt, but I don't think it's necessary, when we have WASM. However, on my demo page, different hash lengths work, hashes are the same.
Hi again, My fault. When I put the hashLen I was thinking about the hex result, not the binary array buffer that is converted to hex. Maybe it's a bit confusing, but closing issue.
Thanks for your time ;)
notice also that argon2 prefixes the salt to the hash, and that its encoded in base64. if you decode just the hash portion (appears after the last dollar ($
)) then you should find the hashLen
matches the byte count exactly. also note sometimes if you don't explicitly specify a salt
value, one is generated randomly for you.
Hi @antelle !
I'm trying to call your argon2-browser implementation in a Chrome PNaCl environment.
I'm doing this:
But when the listener receives the message, the hash length it's always 128. What I'm doing wrong? Is there a bug on the .pexe file?
(If I use AMD it works as expected).
Thanks!