Re: [PATCH security-next v3 16/29] LSM: Prepare for arbitrary LSM enabling

2018-10-01 Thread John Johansen
On 09/24/2018 05:18 PM, Kees Cook wrote: > Before now, all the LSMs that did not specify an "enable" variable in their > struct lsm_info were considered enabled by default. This prepares to make > LSM enabling more explicit. For all LSMs without an explicit "enable" > variable, a hard-coded storage

[PATCH security-next v3 16/29] LSM: Prepare for arbitrary LSM enabling

2018-09-24 Thread Kees Cook
Before now, all the LSMs that did not specify an "enable" variable in their struct lsm_info were considered enabled by default. This prepares to make LSM enabling more explicit. For all LSMs without an explicit "enable" variable, a hard-coded storage location is chosen, and all LSMs without an exte