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
| ||
|
Date: Thu, 19 Oct 2017 23:12:30 +0100 From: David Howells <dhowells@...hat.com> To: Randy Dunlap <rdunlap@...radead.org> Cc: dhowells@...hat.com, linux-security-module@...r.kernel.org, gnomes@...rguk.ukuu.org.uk, linux-efi@...r.kernel.org, matthew.garrett@...ula.com, gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org, jforbes@...hat.com Subject: Re: [PATCH 02/27] Add a SysRq option to lift kernel lockdown Randy Dunlap <rdunlap@...radead.org> wrote: > > +config ALLOW_LOCKDOWN_LIFT > > + bool > > + help > > + Allow the lockdown on a kernel to be lifted, thereby restoring the > > + ability of userspace to access the kernel image (eg. by SysRq+x under > > how about: on > > > + x86). I'll just get rid of this config option, I think - it doesn't make anything available outside of lock_down.c. > > +#ifdef CONFIG_ALLOW_LOCKDOWN_LIFT_BY_KEY > > is that the same as: CONFIG_ALLOW_LOCKDOWN_LIFT_BY_SYSRQ ? > tested? My test machine doesn't have a physical keyboard attached, but you're right. David
Powered by blists - more mailing lists