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
We could want to add a split() or prepare() to remove the $shiro2 and put m and t in the canonical order. Alternatively, for the latter we could patch upstream Argon2 code not to insist on the order, but then there would be more than one representation of the same hash in john.pot, which is undesirable.
The text was updated successfully, but these errors were encountered:
Both userPassword LDAP attributes below encode the password 'secret' using different salts:
userPassword: {ARGON2}$argon2i$v=19$m=4096,t=3,p=1$c2FsdHNhbHQ$DKlexoEJUoZTmkAAC3SaMWk30El9/RvVhlqGo6afIng
userPassword: {ARGON2}$argon2i$v=19$m=4096,t=3,p=1$c2FsdHNhbHRzYWx0$qOCkx9nMeFlaGOO4DUmPDgrlUbgMMuO9T1+vQCFuyzw
solardiz
changed the title
Support Apache Shiro Argon2 hash encoding
Support Apache Shiro and slapd Argon2 hash encodings
Oct 22, 2024
https://shiro.apache.org/cryptography-features.html uses Argon2id hashes, but encodes them subtly differently. Test vectors from CMIYC 2024 cracks:
were after a
sed
crackable by ourargon2-opencl
like this:We could want to add a
split()
orprepare()
to remove the$shiro2
and putm
andt
in the canonical order. Alternatively, for the latter we could patch upstream Argon2 code not to insist on the order, but then there would be more than one representation of the same hash injohn.pot
, which is undesirable.The text was updated successfully, but these errors were encountered: