[lkml]   [2018]   [Oct]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH security-next v4 00/32] LSM: Explict LSM ordering
- add Reviewed-bys.
- cosmetic tweaks.
- New patches to fully centralize LSM "enable" decisions:
LSM: Finalize centralized LSM enabling logic
apparmor: Remove boot parameter
selinux: Remove boot parameter

- add CONFIG_LSM_ENABLE and refactor resulting logic

- add "lsm.order=" and CONFIG_LSM_ORDER instead of overloading "security="
- reorganize introduction of ordering logic code


This refactors the LSM registration and initialization infrastructure to
more centrally support different LSM types for more cleanly supporting the
future expansion of LSM stacking via the "blob-sharing" patch series. What
was considered a "major" LSM is kept for legacy use of the "security="
boot parameter, and now overlaps with the new class of "exclusive" LSMs
for the future blob sharing. The "minor" LSMs become more well defined
as a result of the refactoring.


To better show LSMs activation some debug reporting was added (enabled
with the "lsm.debug" boot commandline option).

I added a WARN() around LSM initialization failures, which appear to
have always been silently ignored. (Realistically any LSM init failures
would have only been due to catastrophic kernel issues that would render
a system unworkable anyway, but it'd be better to expose the problem as
early as possible.)

Instead of continuing to (somewhat improperly) overload the kernel's
initcall system, this changes the LSM infrastructure to store a
registration structure (struct lsm_info) table instead, where metadata
about each LSM can be recorded (name, flags, order, enable flag, init
function). This can be extended in the future to include things like
required blob size for the coming "blob sharing" LSMs.

The "major" LSMs had to individually negotiate which of them should be
enabled. This didn't provide a way to negotiate combinations of other
LSMs (as will be needed for "blob sharing" LSMs). This is solved by
providing the LSM infrastructure with all the details needed to make
the choice (exposing the per-LSM "enabled" flag, if used, the LSM
characteristics, and ordering expectations).

As a result of the refactoring, the "minor" LSMs are able to remove
the open-coded security_add_hooks() calls for "capability", "yama",
and "loadpin", and to redefine "integrity" properly as a general LSM.
(Note that "integrity" actually defined _no_ hooks, but needs the early

With all LSMs being proessed centrally, it was possible to implement
a new boot parameter "lsm.order=" to provide explicit ordering, which
is helpful for the future "blob sharing" LSMs. Matching this is the
provides a higher granularity of control.

Breakdown of patches:

Infrastructure improvements (no logical changes):
LSM: Correctly announce start of LSM initialization Avoid copy/paste of security_init section
LSM: Rename .security_initcall section to .lsm_info
LSM: Remove initcall tracing
LSM: Convert from initcall to struct lsm_info Move LSM_TABLE into INIT_DATA
LSM: Convert security_initcall() into DEFINE_LSM()
LSM: Record LSM name in struct lsm_info
LSM: Provide init debugging infrastructure
LSM: Don't ignore initialization failures

Split "integrity" out into "ordered initialization" (no logical changes):
LSM: Provide separate ordered initialization

Provide centralized LSM enable/disable infrastructure:
LoadPin: Rename "enable" to "enforce"
LSM: Plumb visibility into optional "enabled" state
LSM: Lift LSM selection out of individual LSMs
LSM: Prepare for arbitrary LSM enabling
LSM: Introduce lsm.enable= and lsm.disable=
LSM: Prepare for reorganizing "security=" logic
LSM: Refactor "security=" in terms of enable/disable
LSM: Finalize centralized LSM enabling logic
apparmor: Remove boot parameter
selinux: Remove boot parameter

Provide centralized LSM ordering infrastructure:
LSM: Build ordered list of ordered LSMs for init
LSM: Introduce "lsm.order=" for boottime ordering

Move minor LSMs into ordered LSM initialization:
LoadPin: Initialize as ordered LSM
Yama: Initialize as ordered LSM
LSM: Introduce enum lsm_order
capability: Initialize as LSM_ORDER_FIRST

Move major LSMs into ordered LSM initialization:
LSM: Separate idea of "major" LSM from "exclusive" LSM
LSM: Add all exclusive LSMs to ordered initialization


.../admin-guide/kernel-parameters.txt | 34 +-
arch/arc/kernel/ | 1 -
arch/arm/kernel/ | 1 -
arch/arm64/kernel/ | 1 -
arch/h8300/kernel/ | 1 -
arch/microblaze/kernel/ | 2 -
arch/powerpc/kernel/ | 2 -
arch/um/include/asm/ | 2 -
arch/xtensa/kernel/ | 1 -
include/asm-generic/ | 25 +-
include/linux/init.h | 2 -
include/linux/lsm_hooks.h | 37 +-
include/linux/module.h | 1 -
security/Kconfig | 61 ++--
security/apparmor/Kconfig | 16 -
security/apparmor/lsm.c | 22 +-
security/commoncap.c | 9 +-
security/integrity/iint.c | 6 +-
security/loadpin/Kconfig | 4 +-
security/loadpin/loadpin.c | 29 +-
security/security.c | 343 +++++++++++++++---
security/selinux/Kconfig | 29 --
security/selinux/hooks.c | 32 +-
security/smack/smack_lsm.c | 9 +-
security/tomoyo/tomoyo.c | 8 +-
security/yama/yama_lsm.c | 8 +-
26 files changed, 432 insertions(+), 254 deletions(-)


 \ /
  Last update: 2018-10-02 02:57    [W:0.258 / U:6.716 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site