Skip to main content
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Source Link

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER

Ok, I get that this is an administrative tool and all, but I realized that any user can do ALT + SysRq + C. This link explains what I'm talking about.

But only as root I can do something like echo c > /proc/sysrq-trigger and have it actually crash the system.

If someone has physical access they can just plug in a keyboard and crash the computer (or server), but it would be even harder for them to get root privileges in a terminal, right? Is there a specific reason as to why it works as non-root from a keyboard but only as root from a console?

ThisThis is not what I'm looking for. It is talking about an issue with the Fn part on keyboards. It doesn't even allow you to do it with sudo. You have to first su root.

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER

Ok, I get that this is an administrative tool and all, but I realized that any user can do ALT + SysRq + C. This link explains what I'm talking about.

But only as root I can do something like echo c > /proc/sysrq-trigger and have it actually crash the system.

If someone has physical access they can just plug in a keyboard and crash the computer (or server), but it would be even harder for them to get root privileges in a terminal, right? Is there a specific reason as to why it works as non-root from a keyboard but only as root from a console?

This is not what I'm looking for. It is talking about an issue with the Fn part on keyboards. It doesn't even allow you to do it with sudo. You have to first su root.

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER

Ok, I get that this is an administrative tool and all, but I realized that any user can do ALT + SysRq + C. This link explains what I'm talking about.

But only as root I can do something like echo c > /proc/sysrq-trigger and have it actually crash the system.

If someone has physical access they can just plug in a keyboard and crash the computer (or server), but it would be even harder for them to get root privileges in a terminal, right? Is there a specific reason as to why it works as non-root from a keyboard but only as root from a console?

This is not what I'm looking for. It is talking about an issue with the Fn part on keyboards. It doesn't even allow you to do it with sudo. You have to first su root.

deleted 8 characters in body; edited title
Source Link
Renan
  • 17.4k
  • 8
  • 76
  • 92

In Linux, why do you need root to be root to write to /proc/sysrq-trigger? DO NOT DO THE KEY COMBINATIONS!

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER

Ok, I get that this is an administrative tool and all, but I realized that any user can do

ALT + SYSRQ + C 

ALT + SysRq + C. This link explains what I'm talking about. 

But only as root I can do something like

echo c > /proc/sysrq-trigger 

echo c > /proc/sysrq-trigger and have it actually crash the system.

If someone has physical access they can just plug in a keyboard and crash the computer (or server), but it would be even harder for them to get root privileges in a terminal, right? Is there a specific reason as to why it works as non-root from a keyboard but only as root from a console?

This is not what imI'm looking for. It is talking about an issue with the Fn part on keyboards.

Side note

It doesn't even allow you to do it with sudo. You have to first do,su root.

su root 

In Linux, why do you need root to be root to write to /proc/sysrq-trigger? DO NOT DO THE KEY COMBINATIONS!

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER

Ok, I get that this is an administrative tool and all, but I realized that any user can do

ALT + SYSRQ + C 

This link explains what I'm talking about. But only as root I can do something like

echo c > /proc/sysrq-trigger 

and have it actually crash the system.

If someone has physical access they can just plug in a keyboard and crash the computer (or server), but it would be even harder for them to get root privileges in a terminal, right? Is there a specific reason as to why it works as non-root from a keyboard but only as root from a console?

This is not what im looking for. It is talking about an issue with the Fn part on keyboards.

Side note

It doesn't even allow you to do it with sudo. You have to first do,

su root 

In Linux, why do you need to be root to write to /proc/sysrq-trigger?

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER

Ok, I get that this is an administrative tool and all, but I realized that any user can do ALT + SysRq + C. This link explains what I'm talking about. 

But only as root I can do something like echo c > /proc/sysrq-trigger and have it actually crash the system.

If someone has physical access they can just plug in a keyboard and crash the computer (or server), but it would be even harder for them to get root privileges in a terminal, right? Is there a specific reason as to why it works as non-root from a keyboard but only as root from a console?

This is not what I'm looking for. It is talking about an issue with the Fn part on keyboards. It doesn't even allow you to do it with sudo. You have to first su root.

deleted 13 characters in body
Source Link
Ramesh
  • 40.6k
  • 45
  • 149
  • 222

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER


 

Ok, I get that this is an administrative tool and all, but I realized that any user can do

OK, I get that this is an administrative tool and all, but I realized that anyone (any user) can do
ALT + SYSRQ + C 

This http://en.wikipedia.org/wiki/Reisublink explains about what I'm talking about

 . But! only as root can I can do something like

echo c > /proc/sysrq-trigger 

and have it actually crash the system.

If someone has physical access they can just plug in a keyboardkeyboard and crash the computer (or server), but it would be even harder for them to get root privileges in a terminal, right? Is there a specific reason as to why it works as non-root from a keyboard but only as root from a console?

BTW:
sysrq won't reboot with a keystroke, but will with echo "b" > /proc/sysrq-triggerThis is not what im looking for; itfor. It is talking about an issue with the FnFn part on keyboards.


 

Side note

Side note:
it doesntIt doesn't even allow you to do it with

sudo 

you sudo. You have to first do,

su root 

first

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER


  OK, I get that this is an administrative tool and all, but I realized that anyone (any user) can do
ALT + SYSRQ + C 

http://en.wikipedia.org/wiki/Reisub explains about what I'm talking about

  But! only as root can I do something like

echo c > /proc/sysrq-trigger 

and have it actually crash the system.

If someone has physical access they can just plug in a keyboard and crash the computer (or server), but it would be even harder for them to get root privileges in a terminal, right? Is there a specific reason as to why it works as non-root from a keyboard but only as root from a console?

BTW:
sysrq won't reboot with a keystroke, but will with echo "b" > /proc/sysrq-trigger is not what im looking for; it is talking about an issue with the Fn part on keyboards


 

Side note:
it doesnt even allow you to do it with

sudo 

you have to do

su root 

first

WARNING: THE NEXT KEY COMBINATION WILL CRASH YOUR COMPUTER

Ok, I get that this is an administrative tool and all, but I realized that any user can do

ALT + SYSRQ + C 

This link explains what I'm talking about. But only as root I can do something like

echo c > /proc/sysrq-trigger 

and have it actually crash the system.

If someone has physical access they can just plug in a keyboard and crash the computer (or server), but it would be even harder for them to get root privileges in a terminal, right? Is there a specific reason as to why it works as non-root from a keyboard but only as root from a console?

This is not what im looking for. It is talking about an issue with the Fn part on keyboards.

Side note

It doesn't even allow you to do it with sudo. You have to first do,

su root 
Source Link
Loading