sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc

Bug #1025467 reported by Andy Whitcroft
This bug affects 14 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
In Progress
Andy Whitcroft
procps (Ubuntu)
Fix Released

Bug Description

In fixing Bug #194676 all of the sysrq functionality was disabled. Some options are of low security impact but aid debugabilty of systems. It would be good to reenable what we can. See the original bug for suggested values in use by other distros.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: procps 1:3.3.3-2ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic i686
ApportVersion: 2.3-0ubuntu4
Architecture: i386
Date: Mon Jul 16 23:13:10 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: procps
UpgradeStatus: Upgraded to quantal on 2012-01-04 (194 days ago)

Revision history for this message
Andy Whitcroft (apw) wrote :
Steve Langasek (vorlon)
Changed in procps (Ubuntu):
importance: Undecided → Medium
Steve Langasek (vorlon)
Changed in procps (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package procps - 1:3.3.3-2ubuntu3

procps (1:3.3.3-2ubuntu3) quantal; urgency=low

  * debian/sysctl.d/10-magic-sysrq.conf: adjust to 176 by default, retaining
    support for the critical sync, remount, reboot functions. SysRq+E and
    SysRq+I are still disabled, which unfortunately means SysRq by default
    cannot be used to kill a broken X server; but the only way to enable
    these would be to re-enable SysRq+F, which is one of the options that's
    problematic security-wise. LP: #1025467
 -- Steve Langasek <email address hidden> Mon, 16 Jul 2012 17:06:59 -0700

Changed in procps (Ubuntu):
status: Fix Committed → Fix Released
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
status: New → In Progress
assignee: nobody → Andy Whitcroft (apw)
importance: Undecided → Medium
Revision history for this message
karl (karl-sebastian-liebich) wrote :

is it possible to enable SysRq+K?

Revision history for this message
Wolter HV (wolterh) wrote :

Yes, check out the file /etc/sysctl.conf or /etc/sysctl.d/*magic*.conf. There you will see to what point sysrq is enabled and you may change what to enable in future occasions. To set the enabled features instantaneously you might as well just read the files I listed for documentation, and save the number of your convenience to /proc/sys/kernel/sysrq.

Revision history for this message
geezanansa (geezanansa-ubuntu) wrote :

This affects raring

Revision history for this message
geezanansa (geezanansa-ubuntu) wrote :

Booting Ubuntu Desktop amd64 liveDVD (3.8.0-19-generic) in BIOS mode searching "computer" using file manager to find sysreq settings is now found in /etc/systl.d and named 10-magic-sysrq.conf. Looking in my Ubuntu partitionb which was last bootable using kernel; also confirms sysrq as being disabled by default Can not find why this has been disabled as default so would like to take opportunity to ask; Why is sysrq disabled as default on liveDVD?

Reading the original bug report refers to confirms there may be secuity issues related to this. Is it possible to ask for some reasoning to this? I thought linux had reputation of being secure and virus free!?

Is not a better idea to have sysrq enabled to allow the well known and used RSEIUB(O) if sytem hangs or freezes? At least providing the protection of minimising having to recover sytem files or data due to corrupting hard drive and the need for fsck to kick in or be started manually from recovery.?

Am asking these questions after watching 17 08 2013 episode of the BBC programme ["Click"]( and the "cyberwarfare" article really caught my attention. FAWC

Revision history for this message
geezanansa (geezanansa-ubuntu) wrote :

If sysrq is disabled by default and users are saying it works for them (Ask Ubuntu) ie Perhaps this is evidence of why full disablement of sysrq is applied by default? ie If user did not set sysrq on; Who did?

Revision history for this message
geezanansa (geezanansa-ubuntu) wrote :
Revision history for this message
geezanansa (geezanansa-ubuntu) wrote :

Apologies once again. Now understand S U B are only sysrq commands allowed by default by the use of bitmask 176 which for it is easy to change or adapt relevant settings to any other commands as needed or desired. This for me is applicable to 12.10 and 13.04 desktop amd64. Suprisingly very little information regarding sysrq in Official Ubuntu Documentation. Have posted an answer with much useful information regarding the use and configuration of sysrq in the link posted in last comment. The majority of the answer is copied from another ditrubitions wiki which is based on the Linux Kernel Documentation regarding sysrq. The conclusion to the answer in linked Ask Ubuntu question above is to leave the default settings as is unless there is obvious need to do otherwise. Just use SUB instead of RSEIUB! Tryng sysrq commands in tty will give text output which helps understand and prove there never was a complete disabling of sysrq. Have taken back my affected vote as a little research has proven i am unaffected. Another example of how Ask Ubuntu is a brilliant learning tool and just one of the many brilliant resources available through using Ubuntu! Links provided by mniess in other answer to the same question are key in understanding and appreciating why the need for different bitmask has come about and this is not a new concept.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.