From: "Serge E. Hallyn" <serge@hallyn.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Richard Guy Briggs <rgb@redhat.com>,
cgroups@vger.kernel.org,
Linux Containers <containers@lists.linux-foundation.org>,
Linux API <linux-api@vger.kernel.org>,
Linux Audit <linux-audit@redhat.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Network Development <netdev@vger.kernel.org>,
mszeredi@redhat.com, Andy Lutomirski <luto@kernel.org>,
jlayton@redhat.com, Carlos O'Donell <carlos@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>, Simo Sorce <simo@redhat.com>,
trondmy@primarydata.com, Eric Paris <eparis@parisplace.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: RFC(V3): Audit Kernel Container IDs
Date: Fri, 2 Feb 2018 19:57:21 -0600 [thread overview]
Message-ID: <20180203015721.GB27295@mail.hallyn.com> (raw)
In-Reply-To: <CAHC9VhQ5ciUZDhrsb6S4YxwuzQEY-ra2RTDceWXOdjHEBoZ0BQ@mail.gmail.com>
On Fri, Feb 02, 2018 at 05:05:22PM -0500, Paul Moore wrote:
> On Tue, Jan 9, 2018 at 7:16 AM, Richard Guy Briggs <rgb@redhat.com> wrote:
> > Containers are a userspace concept. The kernel knows nothing of them.
> >
> > The Linux audit system needs a way to be able to track the container
> > provenance of events and actions. Audit needs the kernel's help to do
> > this.
>
> Two small comments below, but I tend to think we are at a point where
> you can start cobbling together some prototype/RFC patches. Surely
Agreed.
LGTM.
> there are going to be a few changes, and new comments, that come out
> once we see an initial implementation so let's see what those are.
thanks,
-serge
prev parent reply other threads:[~2018-02-03 1:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:16 RFC(V3): Audit Kernel Container IDs Richard Guy Briggs
[not found] ` <20180109121620.wi7dq2423ugsraqv-bcJWsdo4jJjeVoXN4CMphl7TgLCtbB0G@public.gmane.org>
2018-01-09 16:18 ` Simo Sorce
2018-01-10 7:00 ` Richard Guy Briggs
2018-02-02 21:24 ` Paul Moore
[not found] ` <CAHC9VhQ=hX55e7ftkVQCogTZTcdSm3rm-+YNOgWomabbXV_sKg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-02 22:19 ` Simo Sorce
2018-02-02 23:24 ` Paul Moore
2018-02-03 19:05 ` Casey Schaufler
[not found] ` <CAHC9VhTg0ocArSek03A-XrbjgR4iGeysxXWaA8HknKBD_5ZRkA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-05 13:47 ` Simo Sorce
[not found] ` <1515514736.3239.10.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-02-02 21:18 ` Paul Moore
2018-01-10 1:05 ` Eric W. Biederman
2018-01-10 6:54 ` Richard Guy Briggs
2018-02-02 22:05 ` Paul Moore
2018-02-03 1:57 ` Serge E. Hallyn [this message]
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=20180203015721.GB27295@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=carlos@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=eparis@parisplace.org \
--cc=jlayton@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-audit@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mszeredi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rgb@redhat.com \
--cc=simo@redhat.com \
--cc=trondmy@primarydata.com \
--cc=viro@zeniv.linux.org.uk \
/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