All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Booth <mbooth@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Format of audit logs
Date: Sun, 13 May 2007 19:17:54 +0100	[thread overview]
Message-ID: <1179080274.4251.19.camel@localhost.localdomain> (raw)
In-Reply-To: <200705131247.47703.sgrubb@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]

On Sun, 2007-05-13 at 12:47 -0400, Steve Grubb wrote:
> On Tuesday 08 May 2007 14:02:06 Matthew Booth wrote:
> > Can anybody point me to a document which describes the format of logs
> > generated by auditd in RHEL 4.
> 
> I have not created such a document. I don't know if anyone else has either. I 
> plan to start creating a bunch of documentation for the audit system this 
> summer.

Ok. In the mean time, can you fill me in on exactly how a PATH record is
added to an event? For example, on execve(), why would I get a PATH
record for both the binary being executed and the ld library? The latter
didn't have a name, just an inode.

Matt
-- 
Matthew Booth, RHCA, RHCSS
Red Hat, Global Professional Services

M:       +44 (0)7977 267231
GPG ID:  D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2007-05-13 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 18:02 Format of audit logs Matthew Booth
2007-05-13 16:47 ` Steve Grubb
2007-05-13 18:17   ` Matthew Booth [this message]
2007-05-13 18:38     ` 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=1179080274.4251.19.camel@localhost.localdomain \
    --to=mbooth@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.