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
Argon2.opslimit_value's documentation, and the ArgumentError it raises, state the value must be in the range of 3..10. This claimed lower limit is incorrect for Argon2id, where OPSLIMIT_MIN is 1.
It seems this leads to some buggy behavior when performing Argon2i operations while Argon2id is available through libsodium.
ok
ok, but...
#<ArgumentError: opslimit must be within the range 1..10>
#<ArgumentError: memlimit must be within the range 2**(13..32)>
ok
#<ArgumentError: opslimit must be within the range 3..10>
#<ArgumentError: memlimit must be within the range 2**(13..32)>
Actual
ok
ok, but...
#<ArgumentError: opslimit must be within the range 3..10> # Incorrect minimum, should be 1
#<ArgumentError: memlimit must be within the range 2**(13..32)>
ok
#<RbNaCl::CryptoError: ARGON2_OUTPUT_PTR_NULL> # oops?
#<ArgumentError: memlimit must be within the range 2**(13..32)>
Also, the documented values for :moderate, :interactive and :sensitive are incorrect for Argon2id.
The text was updated successfully, but these errors were encountered:
Argon2.opslimit_value
's documentation, and the ArgumentError it raises, state the value must be in the range of3..10
. This claimed lower limit is incorrect for Argon2id, where OPSLIMIT_MIN is1
.It seems this leads to some buggy behavior when performing Argon2i operations while Argon2id is available through libsodium.
Reproducer
Expected
Actual
Also, the documented values for
:moderate
,:interactive
and:sensitive
are incorrect for Argon2id.The text was updated successfully, but these errors were encountered: