All of lore.kernel.org
 help / color / mirror / Atom feed
From: LC Bruzenak <lenny@magitekltd.com>
To: "Norman Mark St. Laurent" <mstlaurent@conceras.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] Add auditd listener and remote audit protocol
Date: Tue, 29 Sep 2009 14:14:05 -0500	[thread overview]
Message-ID: <1254251645.9900.23.camel@lcb> (raw)
In-Reply-To: <4AC25718.1050801@conceras.com>

On Tue, 2009-09-29 at 14:51 -0400, Norman Mark St. Laurent wrote:
> Hi LCB,
> 
> I hope I answer u correctly...
> 
> I would look in your /etc/audisp/audisp-remote.conf file and note the 
> port you communicate on, as an alternate you can grab the port with 
> "lsof -i -nP" or "netstat -taupe".  Then you can use tcpdump to watch 
> the connections.
> 
> #tcpdump -i eth0 port 1001     -->  or what ever port you have setup to 
> the remote data on and the correct nic.
> 
> Sounds like this could help u out.
> 
> Norman Mark St. Laurent
> Conceras | Chief Technology Officer and ISSE
> Phone:  703-965-4892
> Email:  mstlaurent@conceras.com
> Web:  http://www.conceras.com
> 
> Connect. Collaborate. Conceras.
> 
> 
> 
> LC Bruzenak wrote:
> > On Thu, 2008-08-14 at 19:31 -0500, LC Bruzenak wrote:
> >   
> >> On Thu, 2008-08-14 at 20:27 -0400, Steve Grubb wrote:
> >>     
> >>> On Thursday 14 August 2008 20:22:24 LC Bruzenak wrote:
> >>>       
> >>>> I think you have a good point - this is the first cut and maybe
> >>>>         
> >> later on
> >>     
> >>>> institute a "replay daemon" or something which can send events on
> >>>> reconnect.
> >>>>         
> >>> Note that all audispd plugins take their input from stdin. At the
> >>>       
> >> worst, if 
> >>     
> >>> you had the time hacks, you could 
> >>>
> >>> ausearch --start <time> --end <time> --raw | /sbin.audisp-remote
> >>>
> >>> -Steve
> >>>       
> >
> > Steve,
> >
> > I have been doing this but I really cannot tell if the audisp-remote
> > connection succeeds; it returns "0" either way.
> > Would there be an easy way to return a non-zero failure indicator?
> >
> > Thx,
> > LCB.
> >

Norman,

Thank for the reply but I wasn't quite clear enough.
The context of this is within a recovery script, so I'm concerned that I
can get the return value of the audisp-remote within the script to
decide if the recovery was successful or if it failed.

I don't think that was clear above; my apologies since the conversation
I referenced was > 1 year old.

LCB.

-- 
LC (Lenny) Bruzenak
lenny@magitekltd.com

  reply	other threads:[~2009-09-29 19:14 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
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 [this message]
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=1254251645.9900.23.camel@lcb \
    --to=lenny@magitekltd.com \
    --cc=linux-audit@redhat.com \
    --cc=mstlaurent@conceras.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.