linux-kernel - Re: [RFC] Input: implement sysrq as an input handler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100319160641.GC16743@khazad-dum.debian.net>
Date:	Fri, 19 Mar 2010 13:06:41 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Linux Input <linux-input@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Jason Wessel <jason.wessel@...driver.com>
Subject: Re: [RFC] Input: implement sysrq as an input handler

On Thu, 18 Mar 2010, Dmitry Torokhov wrote:
> On Thu, Mar 18, 2010 at 09:00:43PM -0300, Henrique de Moraes Holschuh wrote:
> > Any chance of the user being able to avoid the SysRQ events getting to the
> > handle, e.g. by opening the input device in exclusive mode or something like
> > that?
> 
> Yes, it is a possible to suppress SysRq by grabbing an input device.
> This possibility exisst with the current implementation too though -
> after all legacy keyboard driver implemented as an input handler as
> well.
> 
> ... or am I answering a question different from the one you asked? ;)

No, that's exactly what I wanted to know.

What about SAK?  That thing *has* to be untrappable.

Even for the SysRQ debug events, I'd feel better if we could have a class of
system input handlers that cannot be suppressed to use for these things.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/