SUNRPC: Obscure Kerberos integrity keys
authorChuck Lever <chuck.lever@oracle.com>
Sun, 15 Jan 2023 17:21:13 +0000 (12:21 -0500)
committerChuck Lever <chuck.lever@oracle.com>
Mon, 20 Feb 2023 14:20:35 +0000 (09:20 -0500)
commit8270dbfcebea5b68037a84ad1710e2cfa499b82f
tree31714ae4657282fd1f412d3620f8c7c56a9b54e4
parent2dbe0cac3cd6d747579b0b347145326eddfd4e5c
SUNRPC: Obscure Kerberos integrity keys

There's no need to keep the integrity keys around if we instead
allocate and key a pair of ahashes and keep those. This not only
enables the subkeys to be destroyed immediately after deriving
them, but it makes the Kerberos integrity code path more efficient.

Tested-by: Scott Mayhew <smayhew@redhat.com>
Reviewed-by: Simo Sorce <simo@redhat.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
include/linux/sunrpc/gss_krb5.h
net/sunrpc/auth_gss/gss_krb5_crypto.c
net/sunrpc/auth_gss/gss_krb5_mech.c