From: Steve Grubb <sgrubb@redhat.com>
To: Adrian Powell <awp@cray.com>
Cc: linux-audit@redhat.com
Subject: Re: Linux audit newbie question (Sorry probably a little boring...)
Date: Mon, 8 May 2006 11:12:28 -0400 [thread overview]
Message-ID: <200605081112.28425.sgrubb@redhat.com> (raw)
In-Reply-To: <028601c671e5$00134470$03022c0a@kearney>
On Sunday 07 May 2006 10:46, Adrian Powell wrote:
> Thanks for the information. If we were able to go for a 2.6.14
> kernel at some point in the future, would you be fairly confident that this
> syscall auditing code would be maintained in the forseeable future ?.
Yes, it is in the kernel that is distributed by kernel.org. So, it will be
maintained. It is also a main ingrediant for anyone doing CAPP/LSPP
certification. All major distributions and their hardware partners have a
vested interest in doing this, so there should be people to maintain this in
the future.
That said, I don't forsee a lot of maintenance once we are completely done
with it. It is the kind of project that can come to an end and just have
someone watch for changes that may impact the audit system (new syscalls,
changed code paths, etc.)
> It appears that many of the earlier developers have now moved on to other
> things from what I can find. Who is regarded as the definitive developer of
> this code these days ?.
I am for user space side, there is a bunch of people that have worked on the
kernel side of it. This mail list can be used for any questions or concerns
about the native/upstreamed linux kernel audit system for either user space
or kernel.
-Steve
prev parent reply other threads:[~2006-05-08 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 14:11 Linux audit newbie question (Sorry probably a little boring...) Adrian Powell
2006-05-08 14:38 ` Steve Grubb
2006-05-07 14:46 ` Adrian Powell
2006-05-08 15:12 ` 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=200605081112.28425.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=awp@cray.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