[lkml]   [1998]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: SYSRQ accidents
    From: Nathan Hand <>

On Fri, 28 Aug 1998, David Meyer wrote:

> Am I the first one to aim for "k" and accidently hit "l" ? eh? I just
> wanted to saK my current TTY, not destroy my system!

SAK isn't supposed to be a neat toy. It's for developers.

Hmm - sounds like someone who doesnt have a clue what SAK is for.

On the other hand, without enabling SysRq (which is a rather stupid
thing to do, security-wise) the regular SAK only works in normal
keyboard mode, and hence can be spoofed by someone putting the
keyboard in raw or mediumraw mode. In other words, is not absolutely

Maybe the CONFIG_SYSRQ should cover the part of SysRq that no
regular user of the console would ever want (reboot, kill all,
change log level), while the legitimate use (SAK, and perhaps
reset from raw mode) need not be protected by #ifdef CONFIG_SYSRQ .

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.040 / U:6.392 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site