summaryrefslogtreecommitdiffstats
path: root/crypto/echainiv.c
diff options
context:
space:
mode:
authorFrederick Lawler <fred@cloudflare.com>2022-10-17 14:25:00 -0500
committerHerbert Xu <herbert@gondor.apana.org.au>2022-10-28 12:36:34 +0800
commit7984ceb134bf31aa9a597f10ed52d831d5aede14 (patch)
tree47ca0ed4651b0e3b8c616efcdcddf4b4d6df58d8 /crypto/echainiv.c
parent9dcd71c863a6f6476378d076d3e9189c854d49fd (diff)
downloadlinux-7984ceb134bf31aa9a597f10ed52d831d5aede14.tar.bz2
crypto: af_alg - Support symmetric encryption via keyring keys
We want to leverage keyring to store sensitive keys, and then use those keys for symmetric encryption via the crypto API. Among the key types we wish to support are: user, logon, encrypted, and trusted. User key types are already able to have their data copied to user space, but logon does not support this. Further, trusted and encrypted keys will return their encrypted data back to user space on read, which does not make them ideal for symmetric encryption. To support symmetric encryption for these key types, add a new ALG_SET_KEY_BY_KEY_SERIAL setsockopt() option to the crypto API. This allows users to pass a key_serial_t to the crypto API to perform symmetric encryption. The behavior is the same as ALG_SET_KEY, but the crypto key data is copied in kernel space from a keyring key, which allows for the support of logon, encrypted, and trusted key types. Keyring keys must have the KEY_(POS|USR|GRP|OTH)_SEARCH permission set to leverage this feature. This follows the asymmetric_key type where key lookup calls eventually lead to keyring_search_rcu() without the KEYRING_SEARCH_NO_CHECK_PERM flag set. Signed-off-by: Frederick Lawler <fred@cloudflare.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/echainiv.c')
0 files changed, 0 insertions, 0 deletions