public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Robert Evans <bob.evans@jhuapl.edu>
To: linux-audit@redhat.com
Subject: Offline configuration
Date: Fri, 25 May 2007 12:23:40 -0400	[thread overview]
Message-ID: <46570D8C.8090504@jhuapl.edu> (raw)

Hi,

Now that I've got auditing to work on Fedora Core, I have a few more questions.

First, the boxes I've got it working on are connected to the internet and have 
the latest updates.  Now I need to make stuff work on boxes that are *not* 
connected to the internet and are built off of the base CD/DVD.

I know I need the latest versions of the following packages on a system
   audit
   audit-lib
   glibc-kernheaders
   openssh
   openssh-server
   openssh-client
   openssh-askpass
   openssh-askpass-gnome

Do I need the latest of
   audit-libs-devel
   kernel
as well?

Also, what other packages are critical to get NISPOM compliance?  Even when I 
updated the above packages, it didn't look like failed logins on the gnome 
desktop were generating events.  I realize this may be particular to RHEL_64, 
but I also figured I could just have an outdated package.

I'm asking this because when I set up my audit rules on RHEL4_64 with the base 
auditing installed (none of the above updates).  I wasn't getting any 
login/logout events at all, based on my initial experience with the initial 
Fedora configurations, I assume that I need to install updated packages.

I'm not using watches right now, only syscalls, which seem to catch everything I 
need.  It seems like Steve has put enough information in the event logs that it 
is possible to build a GUI that parses, combines, and then displays the event 
logs to the user.  Each displayed event is on a single line and contains the 
pertinent information about the event.

The only gotcha I had with FC5 was that I needed the updated openssh packages to 
generate the events that indicated a logout event for ssh.

Bob Evans
JHU/APL

             reply	other threads:[~2007-05-25 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 16:23 Robert Evans [this message]
2007-05-25 17:57 ` Offline configuration - nice summary of Bob's config Wieprecht, Karen M.
2007-05-25 18:10 ` Offline configuration 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=46570D8C.8090504@jhuapl.edu \
    --to=bob.evans@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