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: "Mickaël Salaün" <mic@digikod.net>, "David S . Miller" <davem@davemloft.net>, "Eric Snowberg" <eric.snowberg@oracle.com>, "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>, "Tyler Hicks" <tyhicks@linux.microsoft.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: [PATCH v8 0/5] Enable root to update the blacklist keyring Date: Mon, 12 Jul 2021 19:03:08 +0200 [thread overview] Message-ID: <20210712170313.884724-1-mic@digikod.net> (raw) Hi, This new patch series is a rebase on v5.14-rc1 . David or Jarkko, if it's still OK with you, could you please push this to linux-next? I successfully tested this patch series with the 211 entries from https://uefi.org/sites/default/files/resources/dbxupdate_x64.bin 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/20210312171232.2681989-1-mic@digikod.net/ Regards, Mickaël Salaün (5): tools/certs: Add print-cert-tbs-hash.sh certs: Check that builtin blacklist hashes are valid certs: Make blacklist_vet_description() more strict certs: Factor out the blacklist hash creation certs: Allow root user to append signed hashes to the blacklist keyring MAINTAINERS | 2 + certs/.gitignore | 1 + certs/Kconfig | 17 +- certs/Makefile | 17 +- certs/blacklist.c | 218 ++++++++++++++---- 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, 346 insertions(+), 80 deletions(-) create mode 100755 scripts/check-blacklist-hashes.awk create mode 100755 tools/certs/print-cert-tbs-hash.sh base-commit: e73f0f0ee7541171d89f2e2491130c7771ba58d3 -- 2.32.0
next reply other threads:[~2021-07-12 17:12 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-12 17:03 Mickaël Salaün [this message] 2021-07-12 17:03 ` [PATCH v8 1/5] tools/certs: Add print-cert-tbs-hash.sh Mickaël Salaün 2021-07-12 17:03 ` [PATCH v8 2/5] certs: Check that builtin blacklist hashes are valid Mickaël Salaün 2021-07-12 17:03 ` [PATCH v8 3/5] certs: Make blacklist_vet_description() more strict Mickaël Salaün 2021-07-12 17:03 ` [PATCH v8 4/5] certs: Factor out the blacklist hash creation Mickaël Salaün 2021-07-12 17:03 ` [PATCH v8 5/5] certs: Allow root user to append signed hashes to the blacklist keyring Mickaël Salaün 2022-03-08 11:53 ` Jarkko Sakkinen 2022-03-08 12:18 ` Mickaël Salaün 2022-03-08 13:19 ` Jarkko Sakkinen 2022-03-08 16:02 ` Mickaël Salaün 2022-03-09 16:01 ` Jarkko Sakkinen 2022-03-09 18:36 ` Mickaël Salaün 2022-03-09 23:11 ` Jarkko Sakkinen 2022-03-11 16:36 ` Mickaël Salaün 2022-03-11 16:45 ` Jarkko Sakkinen 2022-03-30 13:44 ` David Howells 2021-12-13 15:30 ` [PATCH v8 0/5] Enable root to update " Mickaël Salaün 2021-12-21 8:50 ` Jarkko Sakkinen 2022-01-04 15:56 ` Mickaël Salaün 2022-01-06 19:12 ` Jarkko Sakkinen 2022-01-06 19:16 ` Jarkko Sakkinen 2022-01-07 12:14 ` Mickaël Salaün 2022-01-31 11:33 ` Mickaël Salaün 2022-02-17 19:58 ` Jarkko Sakkinen 2022-02-19 11:42 ` 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=20210712170313.884724-1-mic@digikod.net \ --to=mic@digikod.net \ --cc=davem@davemloft.net \ --cc=dhowells@redhat.com \ --cc=dwmw2@infradead.org \ --cc=eric.snowberg@oracle.com \ --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=tyhicks@linux.microsoft.com \ --cc=zohar@linux.ibm.com \ --subject='Re: [PATCH v8 0/5] Enable root to update the blacklist keyring' \ /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
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).