From: Rik van Riel <riel@redhat.com>
To: Kees Cook <keescook@chromium.org>
Cc: Matthew Garrett <matthew.garrett@nebula.com>,
Peter Zijlstra <peterz@infradead.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Eric Biederman <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Vivek Goyal <vgoyal@redhat.com>,
Mel Gorman <mgorman@suse.de>
Subject: Re: [PATCH] kexec: add sysctl to disable kexec
Date: Mon, 09 Dec 2013 18:53:16 -0500 [thread overview]
Message-ID: <52A657EC.6080304@redhat.com> (raw)
In-Reply-To: <20131209233829.GA3501@www.outflux.net>
On 12/09/2013 06:38 PM, Kees Cook wrote:
> For general-purpose (i.e. distro) kernel builds it makes sense to build with
> CONFIG_KEXEC to allow end users to choose what kind of things they want to do
> with kexec. However, in the face of trying to lock down a system with such
> a kernel, there needs to be a way to disable kexec (much like module loading
> can be disabled). Without this, it is too easy for the root user to modify
> kernel memory even when CONFIG_STRICT_DEVMEM and modules_disabled are set.
Not everybody will be running with selinux, or another LSM security
policy, so having this simple knob probably makes sense.
OTOH, are the people who run without a fancy security people the
same people who are interested in locking down the system?
I guess I'll ack the patch, since I see no real downside to having
the knob...
> Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Rik van Riel <riel@redhat.com>
--
All rights reversed
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Matthew Garrett <matthew.garrett@nebula.com>,
Vivek Goyal <vgoyal@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Eric Biederman <ebiederm@xmission.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.de>,
kexec@lists.infradead.org
Subject: Re: [PATCH] kexec: add sysctl to disable kexec
Date: Mon, 09 Dec 2013 18:53:16 -0500 [thread overview]
Message-ID: <52A657EC.6080304@redhat.com> (raw)
In-Reply-To: <20131209233829.GA3501@www.outflux.net>
On 12/09/2013 06:38 PM, Kees Cook wrote:
> For general-purpose (i.e. distro) kernel builds it makes sense to build with
> CONFIG_KEXEC to allow end users to choose what kind of things they want to do
> with kexec. However, in the face of trying to lock down a system with such
> a kernel, there needs to be a way to disable kexec (much like module loading
> can be disabled). Without this, it is too easy for the root user to modify
> kernel memory even when CONFIG_STRICT_DEVMEM and modules_disabled are set.
Not everybody will be running with selinux, or another LSM security
policy, so having this simple knob probably makes sense.
OTOH, are the people who run without a fancy security people the
same people who are interested in locking down the system?
I guess I'll ack the patch, since I see no real downside to having
the knob...
> Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Rik van Riel <riel@redhat.com>
--
All rights reversed
next prev parent reply other threads:[~2013-12-09 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 23:38 [PATCH] kexec: add sysctl to disable kexec Kees Cook
2013-12-09 23:38 ` Kees Cook
2013-12-09 23:53 ` Rik van Riel [this message]
2013-12-09 23:53 ` Rik van Riel
2013-12-10 0:15 ` Kees Cook
2013-12-10 0:15 ` Kees Cook
2013-12-10 0:19 ` Khalid Aziz
2013-12-10 0:19 ` Khalid Aziz
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=52A657EC.6080304@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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 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.