From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "Thomas, Daniel J." <Daniel.Thomas@jhuapl.edu>,
"Wieprecht, Karen M." <Karen.Wieprecht@jhuapl.edu>
Subject: Re: Linux-audit Digest, Vol 27, Issue 2
Date: Mon, 11 Dec 2006 13:20:26 -0500 [thread overview]
Message-ID: <200612111320.27071.sgrubb@redhat.com> (raw)
In-Reply-To: <FC11D747323EB24493CDC753367EEB920170662B@aplesnation.dom1.jhuapl.edu>
On Monday 11 December 2006 12:15, Thomas, Daniel J. wrote:
> I'm new to the audit subsystem. I need to get it working well under
> RHEL4. The version that comes with Redhat is very old (1.0.14?)
That is the latest for RHEL4. There is a 1.0.15 in the pipeline that backports
many features from 1.2.9.
> I noticed if I upgrade to 1.0.14 it pretty much works the same, but if I
> upgrade all the way to 1.3.1, file watch functionality has been removed.
There are differences in the RHEL4 kernel and the current 2.6.19 kernel
regarding audit that causes them to be incompatible in several ways.
> How do I handle auditing of access to security files with 1.3?
1.3.1 is commandline compatible with 1.0.14. However, you need to be using a
2.6.19 kernel for it.
-Steve
next prev parent reply other threads:[~2006-12-11 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061211170024.6F9DF7337D@hormel.redhat.com>
2006-12-11 17:15 ` Linux-audit Digest, Vol 27, Issue 2 Thomas, Daniel J.
2006-12-11 18:20 ` Steve Grubb [this message]
2006-12-11 19:20 ` Thomas, Daniel J.
2006-12-11 19:33 ` Steve Grubb
2006-12-11 20:32 ` Wieprecht, Karen M.
2006-12-11 23:03 ` Steve Grubb
2006-12-12 2:16 ` Wieprecht, Karen M.
2006-12-12 22:08 ` Tools for reviewing audit logs ? Wieprecht, Karen M.
2006-12-12 22:29 ` Steve Grubb
2006-12-13 16:36 ` Jonathan Abbey
2006-12-13 17:21 ` Steve Grubb
2006-12-13 20:12 ` Wieprecht, Karen M.
2006-12-13 16:45 ` Wieprecht, Karen M.
2006-12-13 17:09 ` 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=200612111320.27071.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=Daniel.Thomas@jhuapl.edu \
--cc=Karen.Wieprecht@jhuapl.edu \
--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