From: Ben Hutchings <ben@decadent.org.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>
Cc: Bastian Blank <waldi@debian.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] sysrq: Allow access to sensitive keys to be restricted by default
Date: Mon, 30 Sep 2013 02:31:08 +0100 [thread overview]
Message-ID: <1380504668.14493.22.camel@deadeye.wl.decadent.org.uk> (raw)
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)
Ben.
--- a/include/linux/sysrq.h
+++ b/include/linux/sysrq.h
@@ -18,7 +18,7 @@
#include <linux/types.h>
/* Enable/disable SYSRQ support by default (0==no, 1==yes). */
-#define SYSRQ_DEFAULT_ENABLE 1
+#define SYSRQ_DEFAULT_ENABLE CONFIG_MAGIC_SYSRQ_DEFAULT_MASK
/* Possible values of bitmask for enabling sysrq functions */
/* 0x0001 is reserved for enable everything */
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -312,6 +312,14 @@ config MAGIC_SYSRQ
keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
unless you really know what this hack does.
+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.
+
config DEBUG_KERNEL
bool "Kernel debugging"
help
--
Ben Hutchings
Life is like a sewer:
what you get out of it depends on what you put into it.
next reply other threads:[~2013-09-30 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 1:31 Ben Hutchings [this message]
2013-09-30 1:40 ` Dave Jones
2013-09-30 1:53 ` Greg Kroah-Hartman
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=1380504668.14493.22.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--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®