Re: [PATCH v4 00/10] Enable root to update the blacklist keyring

[PATCH v4 00/10] Enable root to update the blacklist keyring · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 04/10] certs: Fix blacklist flag type confusion · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 09/10] PKCS#7: Fix missing include · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 08/10] certs: Factor out the blacklist hash creation · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 02/10] certs: Check that builtin blacklist hashes are valid · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 10/10] certs: Allow root user to append signed hashes to the blacklist keyring · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 07/10] certs/blacklist: fix kernel doc interface issue · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 05/10] certs: Replace K{U,G}IDT_INIT() with GLOBAL_ROOT_{U,G}ID · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 06/10] certs: Make blacklist_vet_description() more strict · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 03/10] certs: Fix blacklisted hexadecimal hash string check · Mickaël Salaün <mic@digikod.net> · 2021-01-21
[PATCH v4 01/10] tools/certs: Add print-cert-tbs-hash.sh · Mickaël Salaün <mic@digikod.net> · 2021-01-21
Re: [PATCH v4 00/10] Enable root to update the blacklist keyring · David Howells <dhowells@redhat.com> · 2021-01-28
Re: [PATCH v4 00/10] Enable root to update the blacklist keyring · Mickaël Salaün <mic@digikod.net> · 2021-01-28
Re: [PATCH v4 00/10] Enable root to update the blacklist keyring · Mickaël Salaün <mic@digikod.net> · 2021-01-28
Re: [PATCH v4 00/10] Enable root to update the blacklist keyring · Jarkko Sakkinen <jarkko@kernel.org> · 2021-01-30

From: David Howells <dhowells@redhat.com>
Date: 2021-01-28 16:54:37
Also in: keyrings, linux-crypto, linux-security-module, lkml

Hi Mickaël,

I could pull your patches (unless Jarkko wants to), but can you please drop
the patches that are also in my keys-misc branch lest one or other (or both)
of our branches get dropped in the next merge window due to conflicts?

Ideally, can you base your branch on my keys-misc branch?

Thanks,
David

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help