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
Why is the argument of the next_address function not 64-bit little endian?
Right now I am implementing Argon2 for my study.
I was referring to RFCs and papers, but one question occurred to me.
When the RFC requires 32bit little endian, it is implemented as a LE byte array using store32.
However, the input_block input to the next_address function is 64bit and not converted to LE64.
The RFC states the following and also on page 6 of the paper
Even if the subsequent calculation is optimized according to the calculator, the compression function G process itself is not changed, so the output value would be different.
In other words.
Why is the argument of the next_address function not 64-bit little endian?
Right now I am implementing Argon2 for my study.
I was referring to RFCs and papers, but one question occurred to me.
When the RFC requires 32bit little endian, it is implemented as a LE byte array using store32.
However, the input_block input to the next_address function is 64bit and not converted to LE64.
The RFC states the following and also on page 6 of the paper
Even if the subsequent calculation is optimized according to the calculator, the compression function G process itself is not changed, so the output value would be different.
In other words.
This is.
If I don't do this, won't the Argon2i index be different from what is supposed to be?
Thank you in advance.
The text was updated successfully, but these errors were encountered: