[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180203015721.GB27295@mail.hallyn.com>
Date: Fri, 2 Feb 2018 19:57:21 -0600
From: "Serge E. Hallyn" <serge@...lyn.com>
To: Paul Moore <paul@...l-moore.com>
Cc: Richard Guy Briggs <rgb@...hat.com>, cgroups@...r.kernel.org,
Linux Containers <containers@...ts.linux-foundation.org>,
Linux API <linux-api@...r.kernel.org>,
Linux Audit <linux-audit@...hat.com>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Linux Network Development <netdev@...r.kernel.org>,
mszeredi@...hat.com, Andy Lutomirski <luto@...nel.org>,
jlayton@...hat.com, Carlos O'Donell <carlos@...hat.com>,
Al Viro <viro@...iv.linux.org.uk>,
David Howells <dhowells@...hat.com>,
Simo Sorce <simo@...hat.com>, trondmy@...marydata.com,
Eric Paris <eparis@...isplace.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: RFC(V3): Audit Kernel Container IDs
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@...hat.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
Powered by blists - more mailing lists