public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: burn@swtf.dyndns.org
Cc: linux-audit@redhat.com
Subject: Re: Repository of audit events
Date: Wed, 09 Apr 2014 12:32:34 -0400	[thread overview]
Message-ID: <1397061154.23819.20.camel@flatline.rdu.redhat.com> (raw)
In-Reply-To: <1397024726.23793.121.camel@swtf.swtf.dyndns.org>

To the best of my knowledge there is no way to generate every record
type.  I did send sgrubb the beginnings of me trying to write a suite of
programs to exercise some of them for hopeful eventual inclusion in the
auparse checker tool...

I really think such a thing would be useful...

On Wed, 2014-04-09 at 16:25 +1000, Burn Alting wrote:
> All,
> 
> Does there exist a repository of audit events that could be used to test
> changes to the audit parsing code?
> 
> Although turning on 
> 
> -a always,exit -F arch=b32 -S all
> and
> -a always,exit -F arch=b64 -S all
> 
> for a while does tend to generate a lot of audit, but it's clearly not
> exhaustive so I am hoping we have some repositories that are shareable
> and one can test against.
> 
> Rgds
> 
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2014-04-09 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09  6:25 Repository of audit events Burn Alting
2014-04-09 16:32 ` Eric Paris [this message]
2014-04-09 16:33 ` lists_todd
2014-04-09 17:19 ` Steve Grubb
2014-04-10  0:16   ` Burn Alting
2014-04-10  1:26   ` Peter Moody
2014-04-11  3:36     ` Mimi Zohar
2014-04-11 14:07       ` Steve Grubb
2014-04-11 15:26         ` Mimi Zohar

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=1397061154.23819.20.camel@flatline.rdu.redhat.com \
    --to=eparis@redhat.com \
    --cc=burn@swtf.dyndns.org \
    --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