[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <424b4bb4db5c4e126072179ac8ac8fd2@paul-moore.com>
Date: Thu, 31 Oct 2024 18:53:41 -0400
From: Paul Moore <paul@...l-moore.com>
To: Casey Schaufler <casey@...aufler-ca.com>, casey@...aufler-ca.com, linux-security-module@...r.kernel.org
Cc: jmorris@...ei.org, serge@...lyn.com, keescook@...omium.org, john.johansen@...onical.com, penguin-kernel@...ove.sakura.ne.jp, stephen.smalley.work@...il.com, linux-kernel@...r.kernel.org, selinux@...r.kernel.org, mic@...ikod.net
Subject: Re: [PATCH v3 5/5] LSM: secctx provider check on release
On Oct 23, 2024 Casey Schaufler <casey@...aufler-ca.com> wrote:
>
> Verify that the LSM releasing the secctx is the LSM that
> allocated it. This was not necessary when only one LSM could
> create a secctx, but once there can be more than one it is.
>
> Signed-off-by: Casey Schaufler <casey@...aufler-ca.com>
> ---
> security/apparmor/secid.c | 13 +++++--------
> security/selinux/hooks.c | 13 +++++--------
> 2 files changed, 10 insertions(+), 16 deletions(-)
See my note on patch 1/5, merging into lsm/dev.
--
paul-moore.com
Powered by blists - more mailing lists