linux-kernel - Re: [PATCH v2 4/6] Audit: Add record for multiple task security contexts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1958f7b4780.28a7.85c95baa4474aabc7814e68940a78392@paul-moore.com>
Date: Thu, 13 Mar 2025 08:29:36 -0400
From: Paul Moore <paul@...l-moore.com>
To: Casey Schaufler <casey@...aufler-ca.com>, <eparis@...hat.com>, <linux-security-module@...r.kernel.org>, <audit@...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>
Subject: Re: [PATCH v2 4/6] Audit: Add record for multiple task security contexts


On March 12, 2025 7:51:36 PM Paul Moore <paul@...l-moore.com> wrote:
> On Mar  7, 2025 Casey Schaufler <casey@...aufler-ca.com> wrote:

...

>
>> diff --git a/include/linux/security.h b/include/linux/security.h
>> index 540894695c4b..79a9bf4a7cdd 100644
>> --- a/include/linux/security.h
>> +++ b/include/linux/security.h
>> @@ -168,6 +168,7 @@ struct lsm_prop {
>>
>> extern const char *const lockdown_reasons[LOCKDOWN_CONFIDENTIALITY_MAX+1];
>> extern u32 lsm_active_cnt;
>> +extern u32 lsm_subjctx_cnt;
>
> I'm not loving this.  More below, but I'd really like to hide some of
> this detail inside a LSM API/hook if possible.

Thinking more about this I think we can't go with a LSM_MAX_PROPS, or 
similar determined at build time since we have the ability to toggle LSMs 
at boot.  Need to think on this some more, but the answer is going to have 
to be a variable and not a #define.

The LSM init work I'm doing right now directly impacts this, and I'm in the 
final stages now. Let me see what looks reasonable and I'll get back to you.

--
paul-moore.com
>