All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Miloslav Trmač" <mitr@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Cooked audit log format
Date: Mon, 12 May 2008 16:09:40 +0000	[thread overview]
Message-ID: <1210608580.2649.39.camel@amilo> (raw)
In-Reply-To: <1210607435.6847.14.camel@homeserver>

Hello,
LC Bruzenak píše v Po 12. 05. 2008 v 10:50 -0500:
> Q: Will the (hopefully) soon-to-be released visualization tool have any
> influence on this discussion?
I hope so.

>  Also aggregation?
Probably not much.

> Regardless, my original question was would more cooking find its way
> into the visualization tool? And any idea of when that may be released?
A preliminary version will be easily installable in a few days; you can
download a tarball from https://fedorahosted.org/audit-viewer right now,
but building the required python-gtkextra bindings requires some
effort.[1]

audit-viewer currently uses libauparse to interpret field values, and
does not add its own transformations.  Some additional value
transformation / computation is planned, but I'd like to add it to
libauparse, not directly to audit-viewer, to make sure other tools
behave consistently.
	Mirek

[1] You can extract the necessary patches from the Fedora packaging CVS.

  reply	other threads:[~2008-05-12 16:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-11 21:40 Cooked audit log format Matthew Booth
2008-05-12 14:43 ` Steve Grubb
2008-05-12 15:02   ` Matthew Booth
2008-05-12 15:19     ` Steve Grubb
2008-05-12 15:50       ` LC Bruzenak
2008-05-12 16:09         ` Miloslav Trmač [this message]
2008-05-12 16:34           ` Steve Grubb
2008-05-12 16:44             ` LC Bruzenak
2008-05-12 16:53         ` Matthew Booth
2008-05-12 16:12       ` John Dennis
2008-05-12 20:56         ` Eric Paris
2008-05-13 12:30           ` John Dennis
2008-05-15 10:28       ` Tony Jones
2008-05-15 12:44         ` Steve Grubb
2008-05-15 15:59           ` John Dennis

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=1210608580.2649.39.camel@amilo \
    --to=mitr@redhat.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 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.