# Re: \[PATCH security-next v5 00/30\] LSM: Explict ordering

- From: Kees Cook \<hidden\>
- Date: 2018-10-11 15:14:32 
- List: linux-security-module
- Page: https://ratatoskr.run/linux-security-module/2018/10/5405386
- Thread: https://ratatoskr.run/linux-security-module/2018/10/5404915/t.md

```text
On Wed, Oct 10, 2018 at 8:45 PM, James Morris [ref] wrote:
> On Wed, 10 Oct 2018, Kees Cook wrote:
>
>> v5:
>> - redesigned to use CONFIG_LSM= and lsm= for both ordering and enabling
>> - dropped various Reviewed-bys due to rather large refactoring
>
> Patches 1-10 applied to
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
> and next-testing.

Very cool; thanks!

As for the rest, I could post some examples of how the new CONFIG_LSM
and "lsm=..." work (and how they mix with the "legacy" options). Would
that be helpful?

-Kees

-- 
Kees Cook
Pixel Security
```