public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "Kirkwood, David A." <DAVID.A.KIRKWOOD@saic.com>
Subject: Re: RHELU4 versus RHELU5
Date: Thu, 8 Feb 2007 12:33:09 -0500	[thread overview]
Message-ID: <200702081233.09973.sgrubb@redhat.com> (raw)
In-Reply-To: <954E3479CC27224785179CA04904214D04E476BE@0668-its-exmp01.us.saic.com>

On Thursday 08 February 2007 12:06, Kirkwood, David A. wrote:
> Is the auditing used in RHEL4 update 4 a dead end with respect to either
> RHEL4 update 5 or RHEL5?

Within RHEL4, they are very much the same. But some improvements with each 
release. Between RHEL4 & 5, the user interfaces at the program level are the 
same. The audit utilities understand the same parameters, audit.rules has the 
same syntax, etc. The API at the library level has changed somewhat due to 
new capabilities in RHEL5 and the kernel.

> The reason for the question is that I need to write some scripts or
> graphical programs to tie some of the pieces together to construct 
> meaningful auditablity for disjoint items. If I have to do this all over 
> again, are the items going to be the same or completely different or
> somewhat the same?

Between RHEL4 & 5 they are mostly the same. I'd have to know exactly what you 
are trying to do to answer it, but we've worked hard to preserve the same 
command set. IOW, "audit -w /etc/shadow -p wa" runs on each platform. The 
audit records are slightly different format, but contain nearly the same 
information.

> I can use the system as it is now, but I would have to run many ausearches
> and / or aureports with different parameters to get the information I want.
> When I need to look at 10's of systems, it is much easier to consolidate
> everything into a combined output and view the whole thing. 

This is the area that we are working in right now. RHEL4U5 has a realtime 
interface which can be used for log aggregation. We are starting to turn 
attention to that and should start fleshing something out in the coming 
weeks.

-Steve

  reply	other threads:[~2007-02-08 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 16:34 RHELU4 versus RHELU5 Kirkwood, David A.
2007-02-08 16:38 ` Stephen Smalley
2007-02-08 17:06   ` Kirkwood, David A.
2007-02-08 17:33     ` Steve Grubb [this message]
2007-02-08 17:23 ` 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=200702081233.09973.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=DAVID.A.KIRKWOOD@saic.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