Re: [PATCH] LSM: Revive CONFIG_DEFAULT_SECURITY_* for "make oldconfig"

2019-03-29 Thread Tetsuo Handa
On 2019/03/30 4:36, Kees Cook wrote: > Note that since TOMOYO can be fully stacked against the other legacy > major LSMs, when it is selected, it explicitly disables the other LSMs > to avoid them also initializing since TOMOYO does not expect this > currently. Excuse me, but isn't this exception

[PATCH] LSM: Revive CONFIG_DEFAULT_SECURITY_* for "make oldconfig"

2019-03-29 Thread Kees Cook
Commit 70b62c25665f636c ("LoadPin: Initialize as ordered LSM") removed CONFIG_DEFAULT_SECURITY_{SELINUX,SMACK,TOMOYO,APPARMOR,DAC} from security/Kconfig and changed CONFIG_LSM to provide a fixed ordering as a default value. That commit expected that existing users (upgrading from Linux 5.0 and earl