From: Burn Alting <burn.alting@iinet.net.au>
To: Linux-Audit Mailing List <linux-audit@redhat.com>
Subject: BPF audit logs
Date: Wed, 21 Dec 2022 09:36:28 +1100 [thread overview]
Message-ID: <df1eacecc605f856fa80d66d81eddea4dc70ce56.camel@iinet.net.au> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 605 bytes --]
Hi,
I note that the unsolicited AUDIT_BPF audit event only provides a program id and
operation (load or unload). For example, type=BPF msg=audit(21/12/22
09:03:35.765:439) : prog-id=75 op=LOAD or type=BPF msg=audit(21/12/22
09:04:05.883:460) : prog-id=0 op=UNLOAD
I also note that the bpf auxillary structure (struct bpf_prog_aux) that holds the
program id value, also holds a name (struct bpf_prog_aux->name) and uid (struct
bpf_prog_aud->user_struct->uid). Perhaps adding these two items to the AUDIT_BPF
event would provide more security context for this unsolicited event.
Thoughts?
RgdsBurn Alting
[-- Attachment #1.2: Type: text/html, Size: 894 bytes --]
[-- Attachment #2: Type: text/plain, Size: 107 bytes --]
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next reply other threads:[~2022-12-20 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 22:36 Burn Alting [this message]
2022-12-20 23:16 ` BPF audit logs Steve Grubb
2022-12-21 0:01 ` Burn Alting
2022-12-21 14:44 ` Paul Moore
2022-12-21 14:54 ` Paul Moore
2022-12-21 21:02 ` Burn Alting
2022-12-21 23:40 ` Paul Moore
2022-12-21 23:49 ` Burn Alting
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=df1eacecc605f856fa80d66d81eddea4dc70ce56.camel@iinet.net.au \
--to=burn.alting@iinet.net.au \
--cc=burn@swtf.dyndns.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).