lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date: Fri, 14 Mar 2014 12:23:29 -0400
From: Bill Cox <>
Subject: HKDF has collisions with different salts

FYI, if you want to use HKDF and want the output to change with any
change in input, you have to add the salt length to the input key

HKDF inherits the same input collisions from HMAC that PBKDF2
inherited, but they apply to salt instead of the password, which is of
course much better.  Still, I want the output has to change when *any*
input changes, preferably with no known collisions.

Just adding the saltSize parameter to the key material I pass to HKDF.
 That fixes the issue.

Another thing to be careful about: you if you use the
reset/input/result API, you have to zero the context yourself.
hkdfReset does not do it for you.


Powered by blists - more mailing lists