From: Andi Kleen <andi@firstfloor.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Vegard Nossum" <vegard.nossum@gmail.com>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] sysrq-j: emergency shell
Date: Sun, 23 Nov 2008 20:29:49 +0100 [thread overview]
Message-ID: <871vx2jl5e.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20081123001035.64234982@lxorguk.ukuu.org.uk> (Alan Cox's message of "Sun, 23 Nov 2008 00:10:35 +0000")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> But I realize that this does not necessarily mean that the other
>> processes cannot read from or write to the tty anymore. Do you know
>> how to do that? :-)
>
> When you have control vhangup()
It also means more people have to disable sysrq than before.
AFAIK currently it's not possible to actually change anything
with sysrq (just reboot/kill/show information). That would
be the first one who could be actually used to change
data, enable network login etc.
I bet this unexpected change of security policy would
surprise a lot of existing users and suddenly give
a new attack vector.
So if this is added it should at least have a separate
enable switch with default off. But as Alan says, we
have vt-switch anyways so ...
-Andi
--
ak@linux.intel.com
prev parent reply other threads:[~2008-11-23 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 23:51 [RFC][PATCH] sysrq-j: emergency shell Vegard Nossum
2008-11-22 0:42 ` Matt Keenan
2008-11-22 7:19 ` David Newall
2008-11-22 17:27 ` Alexey Dobriyan
2008-11-22 19:07 ` Alan Cox
2008-11-22 22:48 ` Vegard Nossum
2008-11-23 0:10 ` Alan Cox
2008-11-23 19:29 ` Andi Kleen [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=871vx2jl5e.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=adobriyan@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.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.