6 commits

Author	SHA1	Message	Date
Gilles Peskine	3ab121a603	hkdf_expand: explicitly initialize t ... t is never used uninitialized, since the first loop iteration reads 0 bytes of it and then writes hash_len bytes, and subsequent iterations read and write hash_len bytes. However this is somewhat fragile, and it would be legitimate for a static analyzer to be unsure. Initialize t explicitly, to make the code clearer and more robust, at negligible cost. Reported by Vasily Evseenko in https://github.com/ARMmbed/mbedtls/pull/2942 with a slightly different fix. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>	2020-04-02 19:54:51 +02:00
Gilles Peskine	60d6516c60	Fix whitespace style ... Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>	2020-04-02 19:50:00 +02:00
Janos Follath	24eed8d2d2	Initialise return values to an error ... Initialising the return values to and error is best practice and makes the library more robust.	2019-12-03 16:07:18 +00:00
Brian J Murray	ca2ea4e217	Fix issue if salt = NULL and salt_len !=0 in mbedtls_hkdf_extract()	2018-07-23 10:34:47 -07:00
Brian J Murray	a61d123e0e	Minor changes to comments in hkdf.c	2018-07-06 10:02:39 -07:00
Thomas Fossati	656864b360	Add an HKDF (RFC 5869) implementation	2018-06-11 13:10:14 +01:00