From: LC Bruzenak <lenny@magitekltd.com>
To: John Dennis <jdennis@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] Add auditd listener and remote audit protocol
Date: Thu, 14 Aug 2008 18:50:23 -0500 [thread overview]
Message-ID: <1218757823.7022.266.camel@homeserver> (raw)
In-Reply-To: <48A4C1BC.3060309@redhat.com>
On Thu, 2008-08-14 at 19:37 -0400, John Dennis wrote:
> This is why the IPA project has selected AMQP (www.amqp.org) as the
> transport for centralized loggiing (included audit logs). AMQP will
> queue in persistent storage messages which do not reach their
> destination until delivery is assured. The thinking was AMQP was too
> heavy weight a dependency for a simple centralized audit log but makes
> sense in an enterprise deployment such as IPA.
>
I see; thanks for the info John.
Steve did mention this previously to me but I didn't get all the
implications I guess (dense!).
I do require centralized auditing and I also require (more importantly)
not losing any.
I cannot speak for other end-users...but my guess is that if they are
using audit and aggregating they probably care about not dropping it,
whereas others can just syslog the events if the auditd isn't enabled
and then use centralized syslog, right?
AMQP may be heavyweight, however if you start down the road of trying to
not lose networked audit data you probably end up somewhere near there
anyway...
Thx,
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2008-08-14 23:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 21:43 [PATCH] Add auditd listener and remote audit protocol DJ Delorie
2008-08-14 21:58 ` LC Bruzenak
2008-08-14 22:16 ` DJ Delorie
2008-08-14 23:00 ` John Dennis
2008-08-14 23:02 ` LC Bruzenak
2008-08-14 23:16 ` John Dennis
2008-08-14 23:55 ` Steve Grubb
2008-08-14 23:16 ` DJ Delorie
2008-08-14 23:26 ` LC Bruzenak
2008-08-14 23:37 ` John Dennis
2008-08-14 23:50 ` LC Bruzenak [this message]
2008-08-15 0:07 ` Steve Grubb
2008-08-15 0:22 ` LC Bruzenak
2008-08-15 0:27 ` Steve Grubb
2008-08-15 0:31 ` LC Bruzenak
2008-08-15 0:36 ` DJ Delorie
2008-08-15 0:41 ` LC Bruzenak
2009-09-29 17:52 ` LC Bruzenak
2009-09-29 18:51 ` Norman Mark St. Laurent
2009-09-29 19:14 ` LC Bruzenak
2009-09-29 19:27 ` Steve Grubb
2008-08-15 0:23 ` DJ Delorie
2008-08-15 0:04 ` Steve Grubb
2008-08-15 0:19 ` DJ Delorie
2008-08-15 0: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=1218757823.7022.266.camel@homeserver \
--to=lenny@magitekltd.com \
--cc=jdennis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox