From: Matthew Garrett <matthew.garrett@nebula.com>
To: "jerry.hoemann@hp.com" <jerry.hoemann@hp.com>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"keescook@chromium.org" <keescook@chromium.org>,
kexec <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"vgoyal@redhat.com" <vgoyal@redhat.com>
Subject: Re: [PATCH V3 08/11] kexec: Disable at runtime if the kernel enforces module loading restrictions
Date: Wed, 4 Sep 2013 20:12:09 +0000 [thread overview]
Message-ID: <1378325529.13193.8.camel@x230> (raw)
In-Reply-To: <20130904200959.GE8540@anatevka.fc.hp.com>
On Wed, 2013-09-04 at 14:09 -0600, jerry.hoemann@hp.com wrote:
> On Tue, Sep 03, 2013 at 07:50:15PM -0400, Matthew Garrett wrote:
> > kexec permits the loading and execution of arbitrary code in ring 0, which
> > is something that module signing enforcement is meant to prevent. It makes
> > sense to disable kexec in this situation.
> >
> > Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com>
>
>
> Matthew,
>
> Disabling kexec will disable kdump, correct?
Yes.
> Are there plans to enable kdump on a system where secure
> boot is enabled?
Yes, Vivek Goyal (cc:ed) is working on that.
--
Matthew Garrett <matthew.garrett@nebula.com>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next parent reply other threads:[~2013-09-04 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1378252218-18798-1-git-send-email-matthew.garrett@nebula.com>
[not found] ` <1378252218-18798-9-git-send-email-matthew.garrett@nebula.com>
[not found] ` <20130904200959.GE8540@anatevka.fc.hp.com>
2013-09-04 20:12 ` Matthew Garrett [this message]
2013-09-04 20:14 ` [PATCH V3 08/11] kexec: Disable at runtime if the kernel enforces module loading restrictions Josh Boyer
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=1378325529.13193.8.camel@x230 \
--to=matthew.garrett@nebula.com \
--cc=hpa@zytor.com \
--cc=jerry.hoemann@hp.com \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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