Messages in this thread |  | | From | Kees Cook <> | Date | Tue, 2 Oct 2018 16:54:32 -0700 | Subject | Re: [PATCH security-next v4 23/32] selinux: Remove boot parameter |
| |
On Tue, Oct 2, 2018 at 4:46 PM, John Johansen <john.johansen@canonical.com> wrote: > On 10/02/2018 04:06 PM, Kees Cook wrote: >> I think the current proposal (in the other thread) is likely the >> sanest approach: >> >> - Drop CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE >> - Drop CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE >> - All enabled LSMs are listed at build-time in CONFIG_LSM_ENABLE > > Hrrmmm isn't this a Kconfig selectable list, with each built-in LSM > available to be enabled by default at boot.
That's not how I have it currently. It's a comma-separated a string, including the reserved name "all". The default would just be "CONFIG_LSM_ENABLE=all". Casey and I wanted this to have a way to capture new LSMs by default at build-time.
>> - Boot time enabling for selinux= and apparmor= remain >> - lsm.enable= is explicit: overrides above and omissions are disabled > wfm
Okay, this is closer to v3 than v4. Paul or Stephen, how do you feel about losing the SELinux bootparam CONFIG? (i.e. CONFIG_LSM_ENABLE would be replacing its functionality.)
-Kees
-- Kees Cook Pixel Security
|  |