From: dann frazier <dann.frazier@xxxxxxxxxxxxx> The patch that implemented lockdown lifting via SysRq ended up getting dropped[*] before the feature was merged upstream. Having the feature documented but unsupported has caused some confusion for our users. [*] http://archive.lwn.net:8080/linux-kernel/CACdnJuuxAM06TcnczOA6NwxhnmQUeqqm3Ma8btukZpuCS+dOqg@xxxxxxxxxxxxxx/ Signed-off-by: dann frazier <dann.frazier@xxxxxxxxxxxxx> Cc: Heinrich Schuchardt <xypron.glpk@xxxxxx> Cc: David Howells <dhowells@xxxxxxxxxx> Cc: Pedro Principeza <pedro.principeza@xxxxxxxxxxxxx> Cc: Randy Dunlap <rdunlap@xxxxxxxxxxxxx> Cc: Kyle McMartin <kyle@xxxxxxxxxx> Cc: Matthew Garrett <mjg59@xxxxxxxxxx> Signed-off-by: Alejandro Colomar <alx.manpages@xxxxxxxxx> --- man7/kernel_lockdown.7 | 5 ----- 1 file changed, 5 deletions(-) diff --git a/man7/kernel_lockdown.7 b/man7/kernel_lockdown.7 index 30863de62..b0442b3b6 100644 --- a/man7/kernel_lockdown.7 +++ b/man7/kernel_lockdown.7 @@ -33,11 +33,6 @@ where X indicates the process name and Y indicates what is restricted. .PP On an EFI-enabled x86 or arm64 machine, lockdown will be automatically enabled if the system boots in EFI Secure Boot mode. -.PP -If the kernel is appropriately configured, lockdown may be lifted by typing -the appropriate sequence on a directly attached physical keyboard. -For x86 machines, this is -.IR SysRq+x . .\" .SS Coverage When lockdown is in effect, a number of features are disabled or have their -- 2.31.1
