Todd Malsbary bd6972226f mptcp: use untruncated hash in ADD_ADDR HMAC ... There is some ambiguity in the RFC as to whether the ADD_ADDR HMAC is the rightmost 64 bits of the entire hash or of the leftmost 160 bits of the hash. The intention, as clarified with the author of the RFC, is the entire hash. This change returns the entire hash from mptcp_crypto_hmac_sha (instead of only the first 160 bits), and moves any truncation/selection operation on the hash to the caller. Fixes: 12555a2d97 ("mptcp: use rightmost 64 bits in ADD_ADDR HMAC") Reviewed-by: Christoph Paasch <cpaasch@apple.com> Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com> Signed-off-by: Todd Malsbary <todd.malsbary@linux.intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2020-05-22 14:21:24 -07:00
..
crypto.c	mptcp: use untruncated hash in ADD_ADDR HMAC	2020-05-22 14:21:24 -07:00
ctrl.c
diag.c
Kconfig
Makefile
mib.c
mib.h
options.c	mptcp: use untruncated hash in ADD_ADDR HMAC	2020-05-22 14:21:24 -07:00
pm_netlink.c
pm.c
protocol.c	mptcp: Initialize map_seq upon subflow establishment	2020-05-12 12:08:22 -07:00
protocol.h	mptcp: use untruncated hash in ADD_ADDR HMAC	2020-05-22 14:21:24 -07:00
subflow.c	mptcp: use untruncated hash in ADD_ADDR HMAC	2020-05-22 14:21:24 -07:00
token.c