From: Steve Grubb <sgrubb@redhat.com>
To: F Rafi <farhanible@gmail.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: Audit roadmap and new development
Date: Sun, 11 Mar 2018 21:15:02 +0100 [thread overview]
Message-ID: <20180311211502.418679e5@ivy-bridge> (raw)
In-Reply-To: <CABXp1cuaKx+Hh107FA-A1vqg1MhUAu1wvX1BTsKErPrvz6-DXQ@mail.gmail.com>
On Sun, 11 Mar 2018 17:44:39 +0000
F Rafi <farhanible@gmail.com> wrote:
> So container support can be addressed by userspace changes alone
Nope.
> Or will it require kernel audit subsystem updates as well?
The kernel does all the heavy lifting. What this is indicating is that
user space will pick up support to use the kernel's container auditing.
You may have seen a set of patches posted by Richard in the last 2
weeks. That is for the kernel side. There will need to be corresponding
user space code to interface to it. This is probably going to change
events enough that it's again a good reason to break with the old.
-Steve
> On Sun, Mar 11, 2018 at 1:08 PM Paul Moore <paul@paul-moore.com>
> wrote:
>
> > On Sun, Mar 11, 2018 at 5:38 AM, Steve Grubb <sgrubb@redhat.com>
> > wrote:
> > > Hello,
> > >
> > > I wanted to take a few minutes to chat about the future audit
> > > roadmap. The release of audit-2.8.3 represents a breaking
> > > point ...
> >
> > Just a quick note that Steve is talking about the audit userspace
> > which he maintains, the work for the Linux Kernel's audit subsystem
> > is tracked via GitHub (link below). This includes both bug reports
> > *and* new feature requests. If you would like to add to that list,
> > feel free to do so. If you want to help out and contribute,
> > definitely feel free to do so! ;)
> >
> > * https://github.com/linux-audit/audit-kernel/issues
> >
> > --
> > paul moore
> > www.paul-moore.com
> >
> > --
> > Linux-audit mailing list
> > Linux-audit@redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-audit
> >
prev parent reply other threads:[~2018-03-11 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 9:38 Audit roadmap and new development Steve Grubb
2018-03-11 17:07 ` Paul Moore
2018-03-11 17:44 ` F Rafi
2018-03-11 19:24 ` Paul Moore
2018-03-11 20:15 ` Steve Grubb [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=20180311211502.418679e5@ivy-bridge \
--to=sgrubb@redhat.com \
--cc=farhanible@gmail.com \
--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