Bug 2856 - Kernel Alt-sysrq functionality is _dangerous_
Summary: Kernel Alt-sysrq functionality is _dangerous_
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-05-16 22:17 UTC by Chris Evans
Modified: 2008-05-01 15:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-08-31 22:19:12 UTC
Embargoed:


Attachments (Terms of Use)

Description Chris Evans 1999-05-16 22:17:12 UTC
Hi

Before you punt this bug, let me give some background. It is
common, especially in academia, to give console access to
Linux workstations. It is also desirable for these machines
to be secure. This is often done by locking the machine the
keyboard/monitor is attached to, in a cupboard.

In RH5.2, all console "dangers" could be turned off, e.g.
ctrl-alt-del can be disabled in /etc/inittab

RH6.0 introduces 2 new console dangers; reboot/halt via gdm
and kernel alt-sysrq key.

The former may be disabled by editing /etc/X11/gdm/gdm.conf,
but the latter probably can't be turned off easily :-(

So I log this bug so the issue is known about.

Chris

Comment 1 Derek Tattersall 1999-05-20 15:38:59 UTC
Red Hat 6.0 ships with alt+sysreq key combination disabled.  Unless
you explicitly build a kernel with it enabled those keys do
nothing.

The gdm problem is another matter however.

Comment 2 Michael K. Johnson 1999-05-25 18:42:59 UTC
Correction: alt-sysrq is not disabled in Red Hat Linux 6.0

We need to create a kernel patch that creates a sysconf variable
that controls whether alt-sysrq is enabled.  We need to coordinate
this with kernel folks, obviously...

Comment 3 Cristian Gafton 1999-06-16 15:25:59 UTC
Maybe Alan can take a look at this?

Comment 4 Bill Nottingham 1999-08-31 22:19:59 UTC
fixed in initscripts-4.34-1.


Note You need to log in before you can comment on or make changes to this bug.