From: Mimi Zohar <zohar@linux.ibm.com>
To: Eric Snowberg <eric.snowberg@oracle.com>,
jarkko@kernel.org, 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 v2 1/3] KEYS: DigitalSignature link restriction
Date: Tue, 23 May 2023 18:00:59 -0400 [thread overview]
Message-ID: <4df74ef9afdf6ed5a1a65489d1136d825cb391e0.camel@linux.ibm.com> (raw)
In-Reply-To: <20230522230944.180389-2-eric.snowberg@oracle.com>
On Mon, 2023-05-22 at 19:09 -0400, 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>
> Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
Jarkko, please update the above tag to Reviewed-and-tested-by.
--
thanks,
Mimi
next prev parent reply other threads:[~2023-05-23 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 23:09 [PATCH v2 0/3] Add digitalSignature enforcement keyring restrictions Eric Snowberg
2023-05-22 23:09 ` [PATCH v2 1/3] KEYS: DigitalSignature link restriction Eric Snowberg
2023-05-23 22:00 ` Mimi Zohar [this message]
2023-05-22 23:09 ` [PATCH v2 2/3] integrity: Enforce digitalSignature usage in the ima and evm keyrings Eric Snowberg
2023-05-23 22:01 ` Mimi Zohar
2023-05-24 1:22 ` Jarkko Sakkinen
2023-05-24 1:27 ` Jarkko Sakkinen
2023-05-22 23:09 ` [PATCH v2 3/3] integrity: Remove EXPERIMENTAL from Kconfig Eric Snowberg
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=4df74ef9afdf6ed5a1a65489d1136d825cb391e0.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--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=jarkko@kernel.org \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).