From: Vladis Dronov <vdronov@redhat.com>
To: Jiri Benc <jbenc@redhat.com>
Cc: "Rashid Khan" <rkhan@redhat.com>,
"Stanislav Kozina" <skozina@redhat.com>,
"Yauheni Kaliuta" <yauheni.kaliuta@redhat.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
linux-audit@redhat.com,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Petr Matousek" <pmatouse@redhat.com>,
"Jiri Olsa" <jolsa@redhat.com>
Subject: Re: [RFC] audit support for BPF notification
Date: Mon, 4 Nov 2019 08:46:06 -0500 (EST) [thread overview]
Message-ID: <1790619604.12242825.1572875166654.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191104140518.67471654@redhat.com>
[an addition]
I also believe that this log entry should include program source and/or bytecode
checksum so customer/our support can verify that exactly this eBPF program was
loaded/unloaded and not the program that someone states that it was loaded.
Best regards,
Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer
----- Original Message -----
> From: "Jiri Benc" <jbenc@redhat.com>
> To: "Jiri Olsa" <jolsa@redhat.com>
> Cc: "Steve Grubb" <sgrubb@redhat.com>, linux-audit@redhat.com, "Stanislav Kozina" <skozina@redhat.com>, "Yauheni
> Kaliuta" <yauheni.kaliuta@redhat.com>, "Toke Høiland-Jørgensen" <toke@redhat.com>, "Arnaldo Carvalho de Melo"
> <acme@redhat.com>, "Jesper Dangaard Brouer" <brouer@redhat.com>, "Vlad Dronov" <vdronov@redhat.com>, "Petr Matousek"
> <pmatouse@redhat.com>, "Rashid Khan" <rkhan@redhat.com>
> Sent: Monday, November 4, 2019 2:05:18 PM
> Subject: Re: [RFC] audit support for BPF notification
>
> Seems there have been no reply to this...
>
> Jiri, what is the current status?
>
> Vlad, what is the Product Security's view on this? Is the audit support
> for bpf programs loading/unloading a requirement for full support of
> eBPF (as opposed to tech preview)?
>
> Thanks,
>
> Jiri
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2019-11-04 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 14:18 [RFC] audit support for BPF notification Jiri Olsa
2019-08-09 17:45 ` Steve Grubb
2019-08-12 7:59 ` Jiri Olsa
2019-08-12 13:49 ` Steve Grubb
2019-08-12 14:32 ` Jiri Olsa
2019-08-14 7:33 ` Jiri Olsa
2019-08-20 13:54 ` Jiri Olsa
2019-11-04 13:05 ` Jiri Benc
2019-11-04 13:28 ` Jiri Olsa
2019-11-04 13:41 ` Vladis Dronov
2019-11-04 13:46 ` Vladis Dronov [this message]
2019-11-05 0:18 ` Paul Moore
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=1790619604.12242825.1572875166654.JavaMail.zimbra@redhat.com \
--to=vdronov@redhat.com \
--cc=acme@redhat.com \
--cc=brouer@redhat.com \
--cc=jbenc@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-audit@redhat.com \
--cc=pmatouse@redhat.com \
--cc=rkhan@redhat.com \
--cc=skozina@redhat.com \
--cc=toke@redhat.com \
--cc=yauheni.kaliuta@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.