From: David Howells <dhowells@redhat.com>
To: Mehmet Kayaalp <mkayaalp@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, Mimi Zohar <zohar@linux.vnet.ibm.com>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
George Wilson <gcwilson@us.ibm.com>,
LSM <linux-security-module@vger.kernel.org>,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] KEYS: Insert incompressible bytes to reserve space in bzImage
Date: Fri, 25 Nov 2016 09:06:24 +0000 [thread overview]
Message-ID: <14475.1480064784@warthog.procyon.org.uk> (raw)
In-Reply-To: <1479787880-31811-2-git-send-email-mkayaalp@linux.vnet.ibm.com>
Mehmet Kayaalp <mkayaalp@linux.vnet.ibm.com> wrote:
> Include a random filled binary in vmlinux at the space reserved with
> CONFIG_SYSTEM_EXTRA_CERTIFICATE. This results in an uncompressed reserved
> area inside the bzImage as well, so that it can be replaced with an actual
> certificate later (after the bzImage is distributed).
You haven't said *why* you need an incompressible buffer. I presume it's
something to do with the decompression wrapper.
David
next prev parent reply other threads:[~2016-11-25 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 4:11 Mehmet Kayaalp
2016-11-22 4:11 ` [PATCH 1/4] KEYS: Insert incompressible bytes to reserve space in bzImage Mehmet Kayaalp
2016-11-22 4:11 ` [PATCH 2/4] KEYS: Add ELF class-independent certificate insertion support Mehmet Kayaalp
2016-11-22 4:11 ` [PATCH 3/4] KEYS: Support for inserting a certificate into x86 bzImage Mehmet Kayaalp
2016-11-22 4:11 ` [PATCH 4/4] KEYS: Print insert-sys-cert information to stdout instead of stderr Mehmet Kayaalp
2016-11-25 9:06 ` David Howells [this message]
2016-11-25 19:49 ` [PATCH 1/4] KEYS: Insert incompressible bytes to reserve space in bzImage 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=14475.1480064784@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=gcwilson@us.ibm.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mkayaalp@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®