[PATCH 0/2] Allow individual features to be locked down
Paul Moore
paul at paul-moore.com
Sun Apr 13 19:25:08 UTC 2025
On Fri, Mar 21, 2025 at 5:13 PM Paul Moore <paul at paul-moore.com> wrote:
> On Fri, Mar 21, 2025 at 6:24 AM Nikolay Borisov <nik.borisov at suse.com> wrote:
> >
> > This simple change allows usecases where someone might want to lock only specific
> > feature at a finer granularity than integrity/confidentiality levels allows.
> > The first likely user of this is the CoCo subsystem where certain features will be
> > disabled.
> >
> > Nikolay Borisov (2):
> > lockdown: Switch implementation to using bitmap
> > lockdown/kunit: Introduce kunit tests
>
> Hi Nikolay,
>
> Thanks for the patches! With the merge window opening in a few days,
> it is too late to consider this for the upcoming merge window so
> realistically this patchset is two weeks out and I'm hopeful we'll
> have a dedicated Lockdown maintainer by then so I'm going to defer the
> ultimate decision on acceptance to them.
FYI, I expect we'll see something on the mailing list related to this soon.
--
paul-moore.com
More information about the Linux-security-module-archive
mailing list