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: Mon, 25 Oct 2010 10:58:13 -0400 [thread overview]
Message-ID: <201010251058.14207.sgrubb@redhat.com> (raw)
In-Reply-To: <C8EB005E.12CB%kkatzke@sentryds.com>
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.
> Step back to the 1.x arch of autid, although I note that the redhat build is
> 1.7.18 and the changelog doesn¹t seem to have been updated since 1.7.13?
There are 2 changelogs. One for the 2.x branch and one for the 1.8 branch.
What you are seeing is the branch point where 2.x is progressing in its own
way. The other changelog is here:
https://fedorahosted.org/audit/browser/branches/1.8/ChangeLog
-Steve
next prev parent reply other threads:[~2010-10-25 14:58 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 [this message]
2010-10-26 13:34 ` Steve Grubb
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=201010251058.14207.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