From: Matthew Garrett <mjg59@srcf.ucam.org>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH 1/3] Move verifiers to the kernel
Date: Thu, 15 Jun 2017 02:48:41 +0100 [thread overview]
Message-ID: <20170615014841.GA26702@srcf.ucam.org> (raw)
In-Reply-To: <CAEaD8JP2OnTp+goQMOkw=H0ya-wKTdnbhNbGvkeoAP-htchWEA@mail.gmail.com>
On Wed, Jun 14, 2017 at 06:34:38PM -0700, Vladimir 'phcoder' Serbinenko wrote:
> This bid at odds with the need to keep kernel small. Why not just put
> verifiers as the first module to load? Presumably you need to verify the
> whole core in either case.
They're not useful as an external module, so they need to be built into
the core image in any case (otherwise an attacker just replaces the
verifier module…). And if you're making the ordering significant,
it's far too easy for someone to mess up and end up with an insecure
system as a result.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2017-06-15 1:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 0:42 Add TPM support Matthew Garrett
2017-06-15 0:42 ` [PATCH 1/3] Move verifiers to the kernel Matthew Garrett
2017-06-15 1:34 ` Vladimir 'phcoder' Serbinenko
2017-06-15 1:48 ` Matthew Garrett [this message]
2017-06-15 1:52 ` Vladimir 'phcoder' Serbinenko
2017-06-15 3:39 ` Matthew Garrett
2017-06-15 0:42 ` [PATCH 2/3] Verify commands executed by grub Matthew Garrett
2017-06-15 0:42 ` [PATCH 3/3] Core TPM support Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2017-06-15 0:20 Add " Matthew Garrett
2017-06-15 0:21 ` [PATCH 1/3] Move verifiers to the kernel Matthew Garrett
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=20170615014841.GA26702@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=grub-devel@gnu.org \
/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.