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
You used 2^16 instead of 65536 for your test code for the memory usage . The ^ operator here is actually a bitwise xor, not an exponent. With 65536 there it matches the reference binary. :)
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
I'm already using latest.
What operating system and processor architecture are you using (
go env
)?Archlinux from 16.04.2019
CPU:
lscpu
outputgo env
OutputWhat did you do?
I was using argon2 library (golang.org/x/crypto/argon2) and decid thed to check reproducibility of hash result with reference implemetation, which can be found at https://github.com/P-H-C/phc-winner-argon2 (https://godoc.org/golang.org/x/crypto/argon2 has a reference to it).
What did you expect to see?
Executing argon2() with same parameters for x/crypto lib and ref version I would expect at least same hash result and ideally similar execution time.
What did you see instead?
Instead i'v got totally irrelevant results. I'v written program and script for testing:
Here is results.
x/crypto/argon2:
reference binary:
So, am i dumb somewhere or it's just a bug in one of implementations?
The text was updated successfully, but these errors were encountered: