From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Karl Katzke <kkatzke@sentryds.com>
Subject: Re: Which auditd for which kernel?
Date: Tue, 26 Oct 2010 09:34:10 -0400 [thread overview]
Message-ID: <201010260934.11189.sgrubb@redhat.com> (raw)
In-Reply-To: <201010251058.14207.sgrubb@redhat.com>
On Monday, October 25, 2010 10:58:13 am Steve Grubb wrote:
> On Monday, October 25, 2010 10:37:34 am Karl Katzke wrote:
> > What¹s the appropriate response?
>
> You can use either 1.7.18 or 2.0.5 on a 2.6.25 kernel. However, note that
> the audit code has been branched. The 1.7 branch is maintenance only,
> while active development and new features are on the 2.x branch.
Need to make a clarification here. I realized that there were some cleanups
made to libaudit.h so that it would be more manageable going forward. I made
the announcement with the release of 2.0, but forgot about it when answering
your email:
https://www.redhat.com/archives/linux-audit/2009-August/msg00010.html
The short story is 2.0.x wants 2.6.29 or later. If you want to carry a patch,
you can probably add back some necessary defines not provided by your kernel
headers.
-Steve
prev parent reply other threads:[~2010-10-26 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 14:37 Which auditd for which kernel? Karl Katzke
2010-10-25 14:58 ` Steve Grubb
2010-10-26 13:34 ` 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=201010260934.11189.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=kkatzke@sentryds.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