From: Eric Biggers <ebiggers@kernel.org>
To: Frederick Lawler <fred@cloudflare.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net, hch@lst.de,
smueller@chronox.de, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, kernel-team@cloudflare.com,
Ondrej Mosnacek <omosnace@redhat.com>
Subject: Re: [RFC PATCH 1/1] crypto: af_alg - Support symmetric encryption via keyring keys
Date: Tue, 11 Oct 2022 16:07:27 -0700 [thread overview]
Message-ID: <Y0X3L/jhinCqJXxj@sol.localdomain> (raw)
In-Reply-To: <20221004212927.1539105-1-fred@cloudflare.com>
Hi Frederick,
On Tue, Oct 04, 2022 at 04:29:27PM -0500, Frederick Lawler wrote:
> 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 make them not
> 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>
There was a similar patch several years ago by Ondrej Mosnacek:
https://lore.kernel.org/linux-crypto/20190521100034.9651-1-omosnace@redhat.com/T/#u
Have you addressed all the feedback that was raised on that one?
Two random nits below:
> + *dest_len = key->datalen;
> + *dest = kmalloc(*dest_len, GFP_KERNEL);
> + if (!*dest)
> + return -ENOMEM;
> +
> + memcpy(*dest, ukp->data, *dest_len);
This should use kmemdup().
> + } else if (IS_ENABLED(CONFIG_ENCRYPTED_KEYS) &&
> + !strcmp(key->type->name, "encrypted")) {
> + read_key = &read_key_type_encrypted;
> + } else if (IS_ENABLED(CONFIG_TRUSTED_KEYS) &&
> + !strcmp(key->type->name, "trusted")) {
> + read_key = &read_key_type_trusted;
These need to use IS_REACHABLE(), not IS_ENABLED().
- Eric
next prev parent reply other threads:[~2022-10-11 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 21:29 Frederick Lawler
2022-10-11 23:07 ` Eric Biggers [this message]
2022-10-12 14:49 ` Frederick Lawler
2022-10-12 15:21 ` Stephan Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y0X3L/jhinCqJXxj@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=fred@cloudflare.com \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-team@cloudflare.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=smueller@chronox.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®