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: <ea2f0a37-9691-4595-bcb3-881e29d83ee0@juntadeandalucia.es>
Date: Wed, 3 Jan 2024 09:50:54 +0100
From: Luis MuƱoz Fuente <luis.munoz.edu@...tadeandalucia.es>
To: Christian Kujau <lists@...dbynature.de>
Cc: linux-kernel@...r.kernel.org
Subject: Re: I can't activate term(e) and kill(i) magic SysRq key


El 2/1/24 a las 21:45, Christian Kujau escribiĆ³:
> Maybe. Some distributions choose to disable certain sysrq functions. See 
> the page you cited, on the very top: what does "sysctl kernel.sysrq" say? 
> If it's anything but "1", certain or all sysrq functions are disabled.

Hello:
I had gotten involved. I was looking at the option the kernel was
compiled with by default:
grep -i CONFIG_MAGIC_SYSRQ /boot/my_kernel
instead of looking at what option I had chosen:
cat /proc/sys/kernel/sysrq
Thank you


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ