mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-11 12:28:41 +08:00
aefcf2f4b5
Pull kernel lockdown mode from James Morris:
"This is the latest iteration of the kernel lockdown patchset, from
Matthew Garrett, David Howells and others.
From the original description:
This patchset introduces an optional kernel lockdown feature,
intended to strengthen the boundary between UID 0 and the kernel.
When enabled, various pieces of kernel functionality are restricted.
Applications that rely on low-level access to either hardware or the
kernel may cease working as a result - therefore this should not be
enabled without appropriate evaluation beforehand.
The majority of mainstream distributions have been carrying variants
of this patchset for many years now, so there's value in providing a
doesn't meet every distribution requirement, but gets us much closer
to not requiring external patches.
There are two major changes since this was last proposed for mainline:
- Separating lockdown from EFI secure boot. Background discussion is
covered here: https://lwn.net/Articles/751061/
- Implementation as an LSM, with a default stackable lockdown LSM
module. This allows the lockdown feature to be policy-driven,
rather than encoding an implicit policy within the mechanism.
The new locked_down LSM hook is provided to allow LSMs to make a
policy decision around whether kernel functionality that would allow
tampering with or examining the runtime state of the kernel should be
permitted.
The included lockdown LSM provides an implementation with a simple
policy intended for general purpose use. This policy provides a coarse
level of granularity, controllable via the kernel command line:
lockdown={integrity|confidentiality}
Enable the kernel lockdown feature. If set to integrity, kernel features
that allow userland to modify the running kernel are disabled. If set to
confidentiality, kernel features that allow userland to extract
confidential information from the kernel are also disabled.
This may also be controlled via /sys/kernel/security/lockdown and
overriden by kernel configuration.
New or existing LSMs may implement finer-grained controls of the
lockdown features. Refer to the lockdown_reason documentation in
include/linux/security.h for details.
The lockdown feature has had signficant design feedback and review
across many subsystems. This code has been in linux-next for some
weeks, with a few fixes applied along the way.
Stephen Rothwell noted that commit
|
||
|---|---|---|
| .. | ||
| at91_cf.c | ||
| bcm63xx_pcmcia.c | ||
| bcm63xx_pcmcia.h | ||
| cardbus.c | ||
| cirrus.h | ||
| cistpl.c | ||
| cs_internal.h | ||
| cs.c | ||
| db1xxx_ss.c | ||
| ds.c | ||
| electra_cf.c | ||
| i82092.c | ||
| i82092aa.h | ||
| i82365.c | ||
| i82365.h | ||
| Kconfig | ||
| Makefile | ||
| max1600.c | ||
| max1600.h | ||
| o2micro.h | ||
| omap_cf.c | ||
| pcmcia_cis.c | ||
| pcmcia_resource.c | ||
| pd6729.c | ||
| pd6729.h | ||
| pxa2xx_balloon3.c | ||
| pxa2xx_base.c | ||
| pxa2xx_base.h | ||
| pxa2xx_cm_x2xx.c | ||
| pxa2xx_cm_x255.c | ||
| pxa2xx_cm_x270.c | ||
| pxa2xx_colibri.c | ||
| pxa2xx_e740.c | ||
| pxa2xx_hx4700.c | ||
| pxa2xx_mainstone.c | ||
| pxa2xx_palmld.c | ||
| pxa2xx_palmtc.c | ||
| pxa2xx_palmtx.c | ||
| pxa2xx_sharpsl.c | ||
| pxa2xx_stargate2.c | ||
| pxa2xx_trizeps4.c | ||
| pxa2xx_viper.c | ||
| pxa2xx_vpac270.c | ||
| ricoh.h | ||
| rsrc_iodyn.c | ||
| rsrc_mgr.c | ||
| rsrc_nonstatic.c | ||
| sa11xx_base.c | ||
| sa11xx_base.h | ||
| sa1100_generic.c | ||
| sa1100_generic.h | ||
| sa1100_h3600.c | ||
| sa1100_simpad.c | ||
| sa1111_badge4.c | ||
| sa1111_generic.c | ||
| sa1111_generic.h | ||
| sa1111_jornada720.c | ||
| sa1111_lubbock.c | ||
| sa1111_neponset.c | ||
| soc_common.c | ||
| soc_common.h | ||
| socket_sysfs.c | ||
| tcic.c | ||
| tcic.h | ||
| ti113x.h | ||
| topic.h | ||
| vg468.h | ||
| vrc4171_card.c | ||
| vrc4173_cardu.c | ||
| vrc4173_cardu.h | ||
| xxs1500_ss.c | ||
| yenta_socket.c | ||
| yenta_socket.h | ||