mirror of
https://gitlab.com/cryptsetup/cryptsetup.git
synced 2026-01-05 23:15:34 +01:00
PBKDF2 has nasty behaviour that it generates the same output for passwords that has several trailing zero bytes. (IOW null trailing bytes causes collision.) Unfortunatelly our test plays with password length and expect wrong length must always fail. Sometimes the randomly generated key key contains the null byte in the "wrong" place and PBKDF2 causes test to fail. For now, fix it by using fixed keyfile without null bytes (similar to fixed passphrased we already have).
38 KiB
Executable File
38 KiB
Executable File