From: James Morris <jmorris@namei.org>
To: Mehmet Kayaalp <mkayaalp@linux.vnet.ibm.com>
Cc: David Howells <dhowells@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
Keyrings <keyrings@vger.kernel.org>,
Linux Integrity <linux-integrity@vger.kernel.org>,
Linux Security <linux-security-module@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
George Wilson <gcwilson@us.ibm.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: Re: [PATCH v6 0/4] Certificate insertion support for x86 bzImages
Date: Fri, 4 May 2018 03:11:31 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1805040311050.12843@namei.org> (raw)
In-Reply-To: <20180502230811.2751-1-mkayaalp@linux.vnet.ibm.com>
On Wed, 2 May 2018, Mehmet Kayaalp wrote:
> These patches add support for modifying the reserved space for extra
> certificates in a compressed bzImage in x86. This allows separating the
> system keyring certificate from the kernel build process. After the kernel
> image is distributed, the insert-sys-cert script can be used to insert the
> certificate for x86.
Can you provide more explanation of how this is useful and who would use
it?
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2018-05-03 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 23:08 Mehmet Kayaalp
2018-05-02 23:08 ` [PATCH v6 1/4] KEYS: Insert incompressible bytes to reserve space in bzImage Mehmet Kayaalp
2018-05-02 23:08 ` [PATCH v6 2/4] KEYS: Add ELF class-independent certificate insertion support Mehmet Kayaalp
2018-05-02 23:08 ` [PATCH v6 3/4] KEYS: Support for inserting a certificate into x86 bzImage Mehmet Kayaalp
2018-05-02 23:08 ` [PATCH v6 4/4] KEYS: Print insert-sys-cert information to stdout instead of stderr Mehmet Kayaalp
2018-05-03 17:11 ` James Morris [this message]
2018-05-03 21:42 ` [PATCH v6 0/4] Certificate insertion support for x86 bzImages Mimi Zohar
2018-05-04 1:20 ` Mehmet Kayaalp
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=alpine.LRH.2.21.1805040311050.12843@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=gcwilson@us.ibm.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mkayaalp@linux.vnet.ibm.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=stefanb@linux.vnet.ibm.com \
--cc=zohar@linux.vnet.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
all inboxes | Powered by JetHome®