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
| ||
|
Date: Wed, 20 Nov 2019 13:48:56 -0800 From: Alexei Starovoitov <alexei.starovoitov@...il.com> To: Daniel Borkmann <daniel@...earbox.net> Cc: Jiri Olsa <jolsa@...nel.org>, Alexei Starovoitov <ast@...nel.org>, Network Development <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>, Andrii Nakryiko <andriin@...com>, Yonghong Song <yhs@...com>, Martin KaFai Lau <kafai@...com>, Jakub Kicinski <jakub.kicinski@...ronome.com>, Steve Grubb <sgrubb@...hat.com>, David Miller <davem@...hat.com>, Paul Moore <paul@...l-moore.com>, Eric Paris <eparis@...hat.com>, Jiri Benc <jbenc@...hat.com> Subject: Re: [PATCH] bpf: emit audit messages upon successful prog load and unload On Wed, Nov 20, 2019 at 1:46 PM Daniel Borkmann <daniel@...earbox.net> wrote: > > On 11/20/19 10:38 PM, Jiri Olsa wrote: > > From: Daniel Borkmann <daniel@...earbox.net> > > > > Allow for audit messages to be emitted upon BPF program load and > > unload for having a timeline of events. The load itself is in > > syscall context, so additional info about the process initiating > > the BPF prog creation can be logged and later directly correlated > > to the unload event. > > > > The only info really needed from BPF side is the globally unique > > prog ID where then audit user space tooling can query / dump all > > info needed about the specific BPF program right upon load event > > and enrich the record, thus these changes needed here can be kept > > small and non-intrusive to the core. > > > > Raw example output: > > > > # auditctl -D > > # auditctl -a always,exit -F arch=x86_64 -S bpf > > # ausearch --start recent -m 1334 > > [...] > > ---- > > time->Wed Nov 20 12:45:51 2019 > > type=PROCTITLE msg=audit(1574271951.590:8974): proctitle="./test_verifier" > > type=SYSCALL msg=audit(1574271951.590:8974): arch=c000003e syscall=321 success=yes exit=14 a0=5 a1=7ffe2d923e80 a2=78 a3=0 items=0 ppid=742 pid=949 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=2 comm="test_verifier" exe="/root/bpf-next/tools/testing/selftests/bpf/test_verifier" subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=(null) > > type=UNKNOWN[1334] msg=audit(1574271951.590:8974): auid=0 uid=0 gid=0 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=949 comm="test_verifier" exe="/root/bpf-next/tools/testing/selftests/bpf/test_verifier" prog-id=3260 event=LOAD > > ---- > > time->Wed Nov 20 12:45:51 2019 > > type=UNKNOWN[1334] msg=audit(1574271951.590:8975): prog-id=3260 event=UNLOAD > > ---- > > [...] > > > > Signed-off-by: Daniel Borkmann <daniel@...earbox.net> > > Signed-off-by: Jiri Olsa <jolsa@...nel.org> > > LGTM, thanks for the rebase! Applied to bpf-next. Thanks!
Powered by blists - more mailing lists