public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Loredan Stancu <loredan.stancu@myclar.ro>
Cc: linux-audit@redhat.com
Subject: Re: audisp-prelude problems
Date: Wed, 3 Dec 2008 15:22:23 -0500	[thread overview]
Message-ID: <200812031522.24064.sgrubb@redhat.com> (raw)
In-Reply-To: <33375.193.230.245.33.1228327104.squirrel@secure.myclar.ro>

On Wednesday 03 December 2008 12:58:24 you wrote:
> Another question: Can auditd generate events when a user is logging in
> using ssh? That implies ssh use pam?

There are 2 sets of events being sent, auth/acct/session open/close are from 
pam. But cron sends the same events. So, sshd itself sends another event 
USER_LOGIN that is to signify that the pam events are associated with a login 
and what the final result were.


> I ask this because I want use audit in a production server and I'm not
> allowed to manually install packages. I am allowed to only use emerge to
> install packages. At this moment I do not have a USE flag(gentoo specific)
> corresponding to --with-linux-audit.

I guess Gentoo is unpatched. Things will not work right without that last 
patch. All analysis software is predicated on seeing that event.


> @Steve :) : Can you help me please with audisp-remote? I'll explain again
> what I want to do:
> Lets say I have 3 machines(M1 M2 M3). M1 and M2 are 2 server production.
> M3 is a centralized machine events. On M1 and M2 runs auditd and
> audisp-remote.
> audisp-remote sends events to M3. I know how to configure auditd and
> audisp-remote on M1 and M3. What I don't know is what should I do on M3 so
> that it can receive events from M1 and M2 and store this events in regular
> file.

You only have to set its tcp_listen_port to the same one that M1 & M2 are 
trying to connect on, update tcp_wrappers hosts.allow file to allow M1 & M2 to 
connect, then if you have selinux, you need to tell it what port you are 
using, and you also need to punch a hole in your firewall for that port.


> > And you are able to load and list the 2 rules I sent above? Can you find
> > the results with ausearch --start today -k mkexe -m SYSCALL ? 
>
> Yes, I could load that rules and this is what si loaded when a file gets
> eecution rights:

This looks fine. It should be working for you, then.

-Steve

  reply	other threads:[~2008-12-03 20:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 17:58 audisp-prelude problems Loredan Stancu
2008-12-03 20:22 ` Steve Grubb [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-04 15:38 Loredan Stancu
2008-12-04 15:56 ` Steve Grubb
2008-12-04 14:57 Loredan Stancu
2008-12-04 15:33 ` Steve Grubb
2008-12-04 13:10 Loredan Stancu
2008-12-04 13:41 ` Steve Grubb
2008-12-03 16:53 Loredan Stancu
2008-12-03 17:02 ` Steve Grubb
2008-12-03 17:17 ` LC Bruzenak
2008-12-03 17:34   ` Steve Grubb
2008-12-03 16:38 LC Bruzenak
2008-12-03 15:28 Loredan Stancu
2008-12-03 16:33 ` Steve Grubb
2008-12-03 10:23 Loredan Stancu
2008-12-03 13:46 ` Steve Grubb
2008-12-03 15:17   ` LC Bruzenak

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=200812031522.24064.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=loredan.stancu@myclar.ro \
    /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