On Thu, 9 Nov 2017 17:30:36 +0000 David Howells [off-list ref] wrote:
Here's a set of patches to institute a "locked-down mode" in the kernel and
to trigger that mode if the kernel is booted in secure-boot mode or through
the command line.
Enabling CONFIG_LOCK_DOWN_KERNEL makes lockdown mode available.
Enabling CONFIG_ALLOW_LOCKDOWN_LIFT_BY_SYSRQ will allow a SysRq combination
to lift the lockdown. On x86 this is SysRq+x. The keys must be pressed on
an attached keyboard.
Enabling CONFIG_LOCK_DOWN_IN_EFI_SECURE_BOOT will cause EFI secure boot to
trigger kernel lockdown.
Inside the kernel, kernel_is_locked_down() is used to check if the kernel
is in lockdown mode.
Note that the secure boot mode entry doesn't work if the kernel is booted
from older versions of i386/x86_64 Grub as there's a bug in Grub whereby it
doesn't initialise the boot_params correctly. The incorrect initialisation
causes sanitize_boot_params() to be triggered, thereby zapping the secure
boot flag determined by the EFI boot wrapper.
A manual page, kernel_lockdown.7, is proposed, to which people will be
directed by messages in dmesg. This lists the features that are restricted
amongst other things. [Note: I need to update this to mention IMA, so I'll
reply with that later].
I saw all this pop up in linux-next and got curious.
This changelog didn't uncurious me at all. The
LOCK_DOWN_IN_EFI_SECURE_BOOT Kconfig help is unilluminating. A bit of
googling led me to kernel_lockdown.7 (https://lwn.net/Articles/735564/)
which kinda helped.
But still. This is a big, straggly feature and presumably is still
missing things and presumably will require ongoing maintenance as we
add new kernel capabilities. What do we get in return for all of this?
What are the usecases for this feature and why would anyone want one?
What's the value to our users?
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html