From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dave Jones <davej@redhat.com>,
Ben Hutchings <ben@decadent.org.uk>, Jiri Slaby <jslaby@suse.cz>,
Bastian Blank <waldi@debian.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sysrq: Allow access to sensitive keys to be restricted by default
Date: Sun, 29 Sep 2013 18:53:05 -0700 [thread overview]
Message-ID: <20130930015305.GE13344@kroah.com> (raw)
In-Reply-To: <20130930014009.GA30635@redhat.com>
On Sun, Sep 29, 2013 at 09:40:09PM -0400, Dave Jones wrote:
> On Mon, Sep 30, 2013 at 02:31:08AM +0100, Ben Hutchings wrote:
> > From: Bastian Blank <waldi@debian.org>
> >
> > Add a Kconfig variable to set the initial value of the Magic SysRq mask
> > (sysctl: kernel.sysrq).
> >
> > Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> > ---
> > This has been in Debian for a while, but should probably be signed-off
> > by Bastian as well.
> >
> > Debian sets this to 0x01b6, which excludes.
> >
> > 8 - enable debugging dumps of processes etc.
> > 64 - enable signalling of processes (term, kill, oom-kill)
> > ...
> >
> > +config MAGIC_SYSRQ_DEFAULT_MASK
> > + hex "Default mask for Magic SysRq keys on the console"
> > + depends on MAGIC_SYSRQ
> > + default 1
> > + help
> > + Specifies the default mask for the allowed SysRq keys. This can be
> > + used to disable several sensitive keys by default.
>
> Might be nice to have the mask values duplicated here to save having to
> go grepping through code ?
Yeah, a hit would be good. Like what '1' does as default would be a
nice start :)
thanks,
greg k-h
prev parent reply other threads:[~2013-09-30 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 1:31 Ben Hutchings
2013-09-30 1:40 ` Dave Jones
2013-09-30 1:53 ` Greg Kroah-Hartman [this message]
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=20130930015305.GE13344@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben@decadent.org.uk \
--cc=davej@redhat.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=waldi@debian.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 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®