From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: [PATCH v26 22/25] Audit: Add new record for multiple process LSM attributes
Date: Sat, 22 May 2021 22:00:22 -0400 [thread overview]
Message-ID: <2582635.mvXUDI8C0e@x2> (raw)
In-Reply-To: <d753115f-6cbd-0886-473c-b10485cb7c52@schaufler-ca.com>
On Friday, May 21, 2021 6:05:41 PM EDT Casey Schaufler wrote:
> >> The record is produced only in cases where there is more than one
> >> security module with a process "context".
> >> In cases where this record is produced the subj= fields of
> >> other records in the audit event will be set to "subj=?".
> >>
> >> An example of the MAC_TASK_CONTEXTS (1420) record is:
> >>
> >> type=UNKNOWN[1420]
> >> msg=audit(1600880931.832:113)
> >> subj_apparmor==unconfined
> >
> > It should be just a single "=" in the line above.
>
> AppArmor provides the 2nd "=" as part of the subject context.
> What's here is correct. I won't argue that it won't case confusion
> or worse.
We have a specification for a very long time:
https://github.com/linux-audit/audit-documentation/wiki/SPEC-Writing-Good-Events
Everyone has to obey rules or no tools work.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2021-05-23 2:00 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210513200807.15910-1-casey.ref@schaufler-ca.com>
2021-05-13 20:07 ` [PATCH v26 00/25] LSM: Module stacking for AppArmor Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 01/25] LSM: Infrastructure management of the sock security Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 02/25] LSM: Add the lsmblob data structure Casey Schaufler
2021-05-22 8:39 ` Mickaël Salaün
2021-05-25 23:52 ` Casey Schaufler
2021-05-26 9:53 ` Mickaël Salaün
2021-05-13 20:07 ` [PATCH v26 03/25] LSM: provide lsm name and id slot mappings Casey Schaufler
2021-05-14 19:00 ` Kees Cook
2021-05-21 20:18 ` Paul Moore
2021-05-13 20:07 ` [PATCH v26 04/25] IMA: avoid label collisions with stacked LSMs Casey Schaufler
2021-05-14 19:00 ` Kees Cook
2021-05-13 20:07 ` [PATCH v26 05/25] LSM: Use lsmblob in security_audit_rule_match Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 06/25] LSM: Use lsmblob in security_kernel_act_as Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 07/25] LSM: Use lsmblob in security_secctx_to_secid Casey Schaufler
2021-05-14 19:03 ` Kees Cook
2021-05-21 20:18 ` Paul Moore
2021-05-13 20:07 ` [PATCH v26 08/25] LSM: Use lsmblob in security_secid_to_secctx Casey Schaufler
2021-05-14 19:05 ` Kees Cook
2021-05-21 20:18 ` Paul Moore
2021-05-13 20:07 ` [PATCH v26 09/25] LSM: Use lsmblob in security_ipc_getsecid Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 10/25] LSM: Use lsmblob in security_task_getsecid Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 11/25] LSM: Use lsmblob in security_inode_getsecid Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 12/25] LSM: Use lsmblob in security_cred_getsecid Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 13/25] IMA: Change internal interfaces to use lsmblobs Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 14/25] LSM: Specify which LSM to display Casey Schaufler
2021-05-14 19:23 ` Kees Cook
2021-05-17 19:52 ` Casey Schaufler
2021-05-21 20:19 ` Paul Moore
2021-05-13 20:07 ` [PATCH v26 15/25] LSM: Ensure the correct LSM context releaser Casey Schaufler
2021-05-21 20:19 ` Paul Moore
2021-05-13 20:07 ` [PATCH v26 16/25] LSM: Use lsmcontext in security_secid_to_secctx Casey Schaufler
2021-05-13 20:07 ` [PATCH v26 17/25] LSM: Use lsmcontext in security_inode_getsecctx Casey Schaufler
2021-05-14 19:24 ` Kees Cook
2021-05-13 20:08 ` [PATCH v26 18/25] LSM: security_secid_to_secctx in netlink netfilter Casey Schaufler
2021-05-21 20:19 ` Paul Moore
2021-05-13 20:08 ` [PATCH v26 19/25] NET: Store LSM netlabel data in a lsmblob Casey Schaufler
2021-05-13 20:08 ` [PATCH v26 20/25] LSM: Verify LSM display sanity in binder Casey Schaufler
2021-05-13 20:08 ` [PATCH v26 21/25] audit: add support for non-syscall auxiliary records Casey Schaufler
2021-05-21 20:19 ` Paul Moore
2021-05-13 20:08 ` [PATCH v26 22/25] Audit: Add new record for multiple process LSM attributes Casey Schaufler
2021-05-21 20:19 ` Paul Moore
2021-05-21 21:26 ` Richard Guy Briggs
2021-05-21 22:05 ` Casey Schaufler
2021-05-22 2:20 ` Paul Moore
2021-05-22 12:58 ` Richard Guy Briggs
2021-05-23 2:00 ` Steve Grubb [this message]
2021-05-24 15:53 ` Casey Schaufler
2021-05-24 16:06 ` Steve Grubb
2021-05-25 16:26 ` Casey Schaufler
2021-05-25 17:28 ` Casey Schaufler
2021-05-25 18:23 ` Richard Guy Briggs
2021-05-25 19:06 ` Casey Schaufler
2021-05-25 20:08 ` Richard Guy Briggs
2021-05-25 22:46 ` Casey Schaufler
2021-05-13 20:08 ` [PATCH v26 23/25] Audit: Add a new record for multiple object " Casey Schaufler
2021-05-13 20:08 ` [PATCH v26 24/25] LSM: Add /proc attr entry for full LSM context Casey Schaufler
2021-05-13 20:08 ` [PATCH v26 25/25] AppArmor: Remove the exclusive flag Casey Schaufler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2582635.mvXUDI8C0e@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox