From: Mehmet Kayaalp <mkayaalp@linux.vnet.ibm.com>
To: David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-ima-devel@lists.sourceforge.net, keyrings@vger.kernel.org
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
George Wilson <gcwilson@us.ibm.com>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
Mehmet Kayaalp <mkayaalp@linux.vnet.ibm.com>
Subject: [PATCH 0/3 v2] Certificate insertion support for x86 bzImages
Date: Wed, 22 Jun 2016 18:37:30 -0400 [thread overview]
Message-ID: <1466635053-30512-1-git-send-email-mkayaalp@linux.vnet.ibm.com> (raw)
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.
Changes:
* Rebased 2/3 on top of be1fb0e8eb082 ("kbuild: delete unnecessary "@:"")
Mehmet Kayaalp (3):
KEYS: Support for inserting a certificate into x86 bzImage
KEYS: Insert incompressible bytes to vmlinux to reserve space in
bzImage
KEYS: Print insert-sys-cert information to stdout instead of stderr
arch/x86/boot/compressed/Makefile | 8 ++
scripts/insert-sys-cert.c | 212 ++++++++++++++++++++++++++++++++++++--
2 files changed, 212 insertions(+), 8 deletions(-)
--
2.7.4
next reply other threads:[~2016-06-22 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 22:37 Mehmet Kayaalp [this message]
2016-06-22 22:37 ` [PATCH 1/3 v2] KEYS: Support for inserting a certificate into x86 bzImage Mehmet Kayaalp
2016-06-22 22:37 ` [PATCH 2/3 v2] KEYS: Insert incompressible bytes to vmlinux to reserve space in bzImage Mehmet Kayaalp
2016-06-23 6:17 ` kbuild test robot
2016-06-22 22:37 ` [PATCH 3/3 v2] KEYS: Print insert-sys-cert information to stdout instead of stderr 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=1466635053-30512-1-git-send-email-mkayaalp@linux.vnet.ibm.com \
--to=mkayaalp@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=gcwilson@us.ibm.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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®