From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul@paul-moore.com>,
richard Guy Briggs <rgb@redhat.com>,
"linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: LSM stacking v30 Audit changes
Date: Mon, 29 Nov 2021 11:27:44 -0800 [thread overview]
Message-ID: <f3939051-089a-8264-e389-1055bfb9ae35@schaufler-ca.com> (raw)
In-Reply-To: f3939051-089a-8264-e389-1055bfb9ae35.ref@schaufler-ca.com
It would be really, really helpful if I could be feedback
on the v30 LSM stacking patches approach to gathering
supplemental audit records. I used a list scheme so as
to support other uses, such as container ID records. It's
what I would want. It's an easy change if it isn't what
y'all want. I'm eager to get this resolved.
Thank you.
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next parent reply other threads:[~2021-11-29 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f3939051-089a-8264-e389-1055bfb9ae35.ref@schaufler-ca.com>
2021-11-29 19:27 ` Casey Schaufler [this message]
2021-11-29 19:54 ` LSM stacking v30 Audit changes Paul Moore
2021-11-29 20:05 ` 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=f3939051-089a-8264-e389-1055bfb9ae35@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=linux-audit@redhat.com \
--cc=paul@paul-moore.com \
--cc=rgb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).