From: "Mickaël Salaün" <mic@digikod.net>
To: David Howells <dhowells@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
Jarkko Sakkinen <jarkko@kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"James Morris" <jmorris@namei.org>,
"Mickaël Salaün" <mic@linux.microsoft.com>,
"Mimi Zohar" <zohar@linux.ibm.com>,
"Serge E . Hallyn" <serge@hallyn.com>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Enable root to update the blacklist keyring
Date: Tue, 5 Jan 2021 11:12:57 +0100 [thread overview]
Message-ID: <67945fa6-2796-bfcd-5541-d54662e9802a@digikod.net> (raw)
In-Reply-To: <20201211190330.2586116-1-mic@digikod.net>
Jarkko, David, what is the status of this patch series? Do you need help
to test it?
On 11/12/2020 20:03, Mickaël Salaün wrote:
> Hi,
>
> This second patch series includes some minor fixes and remove the 4 fix
> patches picked by David Howells. This patch series can then be applied
> on top of
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-fixes
>
> The goal of these patches is to add a new configuration option to enable
> the root user to load signed keys in the blacklist keyring. This
> keyring is useful to "untrust" certificates or files. Enabling to
> safely update this keyring without recompiling the kernel makes it more
> usable.
>
> Previous patch series:
> https://lore.kernel.org/lkml/20201120180426.922572-1-mic@digikod.net/
>
> Regards,
>
> Mickaël Salaün (5):
> certs: Make blacklist_vet_description() more strict
> certs: Factor out the blacklist hash creation
> certs: Check that builtin blacklist hashes are valid
> certs: Allow root user to append signed hashes to the blacklist
> keyring
> tools/certs: Add print-cert-tbs-hash.sh
>
> MAINTAINERS | 2 +
> certs/.gitignore | 1 +
> certs/Kconfig | 10 +
> certs/Makefile | 15 +-
> certs/blacklist.c | 202 ++++++++++++++----
> crypto/asymmetric_keys/x509_public_key.c | 3 +-
> include/keys/system_keyring.h | 14 +-
> scripts/check-blacklist-hashes.awk | 37 ++++
> .../platform_certs/keyring_handler.c | 26 +--
> tools/certs/print-cert-tbs-hash.sh | 91 ++++++++
> 10 files changed, 326 insertions(+), 75 deletions(-)
> create mode 100755 scripts/check-blacklist-hashes.awk
> create mode 100755 tools/certs/print-cert-tbs-hash.sh
>
>
> base-commit: 1b91ea77dfeb2c5924ab940f2e43177c78a37d8f
>
next prev parent reply other threads:[~2021-01-05 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 19:03 [PATCH v2 0/5] Enable root to update the blacklist keyring Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 1/5] certs: Make blacklist_vet_description() more strict Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 2/5] certs: Factor out the blacklist hash creation Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 3/5] certs: Check that builtin blacklist hashes are valid Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 4/5] certs: Allow root user to append signed hashes to the blacklist keyring Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 5/5] tools/certs: Add print-cert-tbs-hash.sh Mickaël Salaün
2021-01-05 10:12 ` Mickaël Salaün [this message]
2021-01-10 4:57 ` [PATCH v2 0/5] Enable root to update the blacklist keyring Jarkko Sakkinen
2021-01-14 4:15 ` 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=67945fa6-2796-bfcd-5541-d54662e9802a@digikod.net \
--to=mic@digikod.net \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--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=mic@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.