From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Eric Snowberg" <eric.snowberg@oracle.com>, <zohar@linux.ibm.com>,
<dhowells@redhat.com>, <dwmw2@infradead.org>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<dmitry.kasatkin@gmail.com>, <paul@paul-moore.com>,
<jmorris@namei.org>, <serge@hallyn.com>, <jlee@suse.com>,
<kanth.ghatraju@oracle.com>, <konrad.wilk@oracle.com>,
<keyrings@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-crypto@vger.kernel.org>, <linux-integrity@vger.kernel.org>,
<linux-security-module@vger.kernel.org>
Subject: Re: [PATCH 1/3] KEYS: DigitalSignature link restriction
Date: Thu, 11 May 2023 01:34:17 +0300 [thread overview]
Message-ID: <CSIYF14C6N58.7IDA6DAC9NHF@suppilovahvero> (raw)
In-Reply-To: <20230508220708.2888510-2-eric.snowberg@oracle.com>
On Tue May 9, 2023 at 1:07 AM EEST, Eric Snowberg wrote:
> Add a new link restriction. Restrict the addition of keys in a keyring
> based on the key having digitalSignature usage set. Additionally, verify
> the new certificate against the ones in the system keyrings. Add two
> additional functions to use the new restriction within either the builtin
> or secondary keyrings.
>
> Signed-off-by: Eric Snowberg <eric.snowberg@oracle.com>
> ---
> certs/system_keyring.c | 52 +++++++++++++++++++++++++++++++
> crypto/asymmetric_keys/restrict.c | 44 ++++++++++++++++++++++++++
> include/crypto/public_key.h | 11 +++++++
> include/keys/system_keyring.h | 11 +++++++
> 4 files changed, 118 insertions(+)
>
> diff --git a/certs/system_keyring.c b/certs/system_keyring.c
> index a7a49b17ceb1..4249c49bd43b 100644
> --- a/certs/system_keyring.c
> +++ b/certs/system_keyring.c
> @@ -51,6 +51,27 @@ int restrict_link_by_builtin_trusted(struct key *dest_keyring,
> builtin_trusted_keys);
> }
>
> +/**
> + * restrict_link_by_digsig_builtin - Restrict digitalSignature key additions
> + * by the built-in keyring.
BTW, does checkpatch complain if you put that to a single line (I don't
know this)?
If not, I would just put "Restrict by digitalSignature"
> + * @dest_keyring: Keyring being linked to.
> + * @type: The type of key being added.
> + * @payload: The payload of the new key.
> + * @restriction_key: A ring of keys that can be used to vouch for the new cert.
> + *
> + * Restrict the addition of keys into a keyring based on the key-to-be-added
> + * being vouched for by a key in the built in system keyring. The new key
> + * must have the digitalSignature usage field set.
> + */
> +int restrict_link_by_digsig_builtin(struct key *dest_keyring,
> + const struct key_type *type,
> + const union key_payload *payload,
> + struct key *restriction_key)
> +{
> + return restrict_link_by_digsig(dest_keyring, type, payload,
> + builtin_trusted_keys);
> +}
> +
> #ifdef CONFIG_SECONDARY_TRUSTED_KEYRING
> /**
> * restrict_link_by_builtin_and_secondary_trusted - Restrict keyring
> @@ -83,6 +104,37 @@ int restrict_link_by_builtin_and_secondary_trusted(
> secondary_trusted_keys);
> }
>
> +/**
> + * restrict_link_by_digsig_builtin_and_secondary - Restrict digitalSignature
> + * key additions by both built-in and secondary keyrings.
> + * @dest_keyring: Keyring being linked to.
> + * @type: The type of key being added.
> + * @payload: The payload of the new key.
> + * @restrict_key: A ring of keys that can be used to vouch for the new cert.
> + *
> + * Restrict the addition of keys into a keyring based on the key-to-be-added
> + * being vouched for by a key in either the built-in or the secondary system
> + * keyrings. The new key must have the digitalSignature usage field set.
> + */
> +int restrict_link_by_digsig_builtin_and_secondary(
> + struct key *dest_keyring,
> + const struct key_type *type,
> + const union key_payload *payload,
> + struct key *restrict_key)
> +{
> + /* If we have a secondary trusted keyring, then that contains a link
> + * through to the builtin keyring and the search will follow that link.
> + */
> + if (type == &key_type_keyring &&
> + dest_keyring == secondary_trusted_keys &&
> + payload == &builtin_trusted_keys->payload)
> + /* Allow the builtin keyring to be added to the secondary */
> + return 0;
> +
> + return restrict_link_by_digsig(dest_keyring, type, payload,
> + secondary_trusted_keys);
> +}
> +
> /*
> * Allocate a struct key_restriction for the "builtin and secondary trust"
> * keyring. Only for use in system_trusted_keyring_init().
> diff --git a/crypto/asymmetric_keys/restrict.c b/crypto/asymmetric_keys/restrict.c
> index 276bdb627498..6b69ea40da23 100644
> --- a/crypto/asymmetric_keys/restrict.c
> +++ b/crypto/asymmetric_keys/restrict.c
> @@ -148,6 +148,50 @@ int restrict_link_by_ca(struct key *dest_keyring,
> return 0;
> }
>
> +/**
> + * restrict_link_by_digsig - Restrict additions to a ring of digsig keys
> + * @dest_keyring: Keyring being linked to.
> + * @type: The type of key being added.
> + * @payload: The payload of the new key.
> + * @trust_keyring: A ring of keys that can be used to vouch for the new cert.
> + *
> + * Check if the new certificate has digitalSignature usage set. If it is,
> + * then mark the new certificate as being ok to link. Afterwards verify
> + * the new certificate against the ones in the trust_keyring.
> + *
> + * Returns 0 if the new certificate was accepted, -ENOKEY if the
> + * certificate is not a digsig. -ENOPKG if the signature uses unsupported
> + * crypto, or some other error if there is a matching certificate but
> + * the signature check cannot be performed.
> + */
> +int restrict_link_by_digsig(struct key *dest_keyring,
> + const struct key_type *type,
> + const union key_payload *payload,
> + struct key *trust_keyring)
> +{
> + const struct public_key *pkey;
> +
> + if (type != &key_type_asymmetric)
> + return -EOPNOTSUPP;
> +
> + pkey = payload->data[asym_crypto];
> +
> + if (!pkey)
> + return -ENOPKG;
> +
> + if (!test_bit(KEY_EFLAG_DIGITALSIG, &pkey->key_eflags))
> + return -ENOKEY;
> +
> + if (test_bit(KEY_EFLAG_CA, &pkey->key_eflags))
> + return -ENOKEY;
> +
> + if (test_bit(KEY_EFLAG_KEYCERTSIGN, &pkey->key_eflags))
> + return -ENOKEY;
> +
> + return restrict_link_by_signature(dest_keyring, type, payload,
> + trust_keyring);
> +}
> +
> static bool match_either_id(const struct asymmetric_key_id **pair,
> const struct asymmetric_key_id *single)
> {
> diff --git a/include/crypto/public_key.h b/include/crypto/public_key.h
> index 653992a6e941..8eb5eff059f3 100644
> --- a/include/crypto/public_key.h
> +++ b/include/crypto/public_key.h
> @@ -80,6 +80,10 @@ extern int restrict_link_by_ca(struct key *dest_keyring,
> const struct key_type *type,
> const union key_payload *payload,
> struct key *trust_keyring);
> +int restrict_link_by_digsig(struct key *dest_keyring,
> + const struct key_type *type,
> + const union key_payload *payload,
> + struct key *trust_keyring);
> #else
> static inline int restrict_link_by_ca(struct key *dest_keyring,
> const struct key_type *type,
> @@ -88,6 +92,13 @@ static inline int restrict_link_by_ca(struct key *dest_keyring,
> {
> return 0;
> }
> +static inline int restrict_link_by_digsig(struct key *dest_keyring,
> + const struct key_type *type,
> + const union key_payload *payload,
> + struct key *trust_keyring)
> +{
> + return 0;
> +}
> #endif
>
> extern int query_asymmetric_key(const struct kernel_pkey_params *,
> diff --git a/include/keys/system_keyring.h b/include/keys/system_keyring.h
> index 91e080efb918..38f63f1c2cbe 100644
> --- a/include/keys/system_keyring.h
> +++ b/include/keys/system_keyring.h
> @@ -23,10 +23,15 @@ extern int restrict_link_by_builtin_trusted(struct key *keyring,
> const struct key_type *type,
> const union key_payload *payload,
> struct key *restriction_key);
> +int restrict_link_by_digsig_builtin(struct key *dest_keyring,
> + const struct key_type *type,
> + const union key_payload *payload,
> + struct key *restriction_key);
> extern __init int load_module_cert(struct key *keyring);
>
> #else
> #define restrict_link_by_builtin_trusted restrict_link_reject
> +#define restrict_link_by_digsig_builtin restrict_link_reject
>
> static inline __init int load_module_cert(struct key *keyring)
> {
> @@ -41,8 +46,14 @@ extern int restrict_link_by_builtin_and_secondary_trusted(
> const struct key_type *type,
> const union key_payload *payload,
> struct key *restriction_key);
> +extern int restrict_link_by_digsig_builtin_and_secondary(
> + struct key *keyring,
> + const struct key_type *type,
> + const union key_payload *payload,
> + struct key *restriction_key);
> #else
> #define restrict_link_by_builtin_and_secondary_trusted restrict_link_by_builtin_trusted
> +#define restrict_link_by_digsig_builtin_and_secondary restrict_link_by_digsig_builtin
> #endif
>
> #ifdef CONFIG_INTEGRITY_MACHINE_KEYRING
> --
> 2.27.0
BR, Jarkko
next prev parent reply other threads:[~2023-05-10 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 22:07 [PATCH 0/3] Add digitalSignature enforcement keyring restrictions Eric Snowberg
2023-05-08 22:07 ` [PATCH 1/3] KEYS: DigitalSignature link restriction Eric Snowberg
2023-05-10 22:34 ` Jarkko Sakkinen [this message]
2023-05-11 22:48 ` Eric Snowberg
2023-05-17 1:18 ` Mimi Zohar
2023-05-08 22:07 ` [PATCH 2/3] integrity: Enforce digitalSignature usage in the ima and evm keyrings Eric Snowberg
2023-05-17 1:18 ` Mimi Zohar
2023-05-08 22:07 ` [PATCH 3/3] integrity: Remove EXPERIMENTAL from Kconfig Eric Snowberg
2023-05-10 22:42 ` Jarkko Sakkinen
2023-05-17 1:18 ` Mimi Zohar
2023-05-10 22:31 ` [PATCH 0/3] Add digitalSignature enforcement keyring restrictions Jarkko Sakkinen
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=CSIYF14C6N58.7IDA6DAC9NHF@suppilovahvero \
--to=jarkko@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eric.snowberg@oracle.com \
--cc=herbert@gondor.apana.org.au \
--cc=jlee@suse.com \
--cc=jmorris@namei.org \
--cc=kanth.ghatraju@oracle.com \
--cc=keyrings@vger.kernel.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/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