From: Nick Bowler <nbowler@elliptictech.com>
To: David Howells <dhowells@redhat.com>
Cc: =?ISO-8859-2?Q?Arkadiusz_Mi=B6kiewicz?= <a.miskiewicz@gmail.com>,
jmorris@namei.org, linux-security-module@vger.kernel.org,
keyrings@linux-nfs.org, linux-kernel@vger.kernel.org,
dmitry.kasatkin@intel.com, zohar@linux.vnet.ibm.com,
arjan@linux.intel.com, alan@lxorguk.ukuu.org.uk
Subject: Re: [GIT PULL] Crypto keys and module signing
Date: Mon, 12 Dec 2011 09:12:55 -0500 [thread overview]
Message-ID: <20111212141255.GA1105@elliptictech.com> (raw)
In-Reply-To: <21891.1323521411@redhat.com>
On 2011-12-10 12:50 +0000, David Howells wrote:
> Arkadiusz Miśkiewicz <a.miskiewicz@gmail.com> wrote:
> > and prehaps kernel could load keys from initramfs?
>
> How do you trust the keys? If you have a TPM, then yes you can do that.
Exactly the same way you trust the kernel image itself. If you can't
trust the integrity of your initramfs (and thus the keys stored within
it), then you also cannot trust the integrity of the kernel image and
thus this whole signing exercise is moot.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2011-12-12 14:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 14:47 [GIT PULL] Crypto keys and module signing David Howells
2011-12-09 4:05 ` James Morris
2011-12-09 9:17 ` David Howells
2011-12-09 9:35 ` James Morris
2011-12-09 14:20 ` Arjan van de Ven
2011-12-09 14:31 ` James Morris
2011-12-09 18:06 ` David Howells
2011-12-09 18:18 ` Arjan van de Ven
2011-12-09 18:47 ` David Howells
2011-12-09 18:49 ` Arjan van de Ven
2011-12-09 18:59 ` David Howells
2011-12-09 19:41 ` [Keyrings] " Daniel Kahn Gillmor
2011-12-10 9:49 ` Geert Uytterhoeven
2011-12-10 11:42 ` Arkadiusz Miśkiewicz
2011-12-10 12:50 ` David Howells
2011-12-12 14:12 ` Nick Bowler [this message]
2011-12-10 18:54 ` Arjan van de Ven
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=20111212141255.GA1105@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=a.miskiewicz@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.