All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Jan-Frode Myklebust <janfrode@tanso.net>
Cc: selinux@tycho.nsa.gov
Subject: Re: setroubleshooter/sealert on central loghost?
Date: Thu, 02 Aug 2007 10:15:53 -0400	[thread overview]
Message-ID: <46B1E719.500@redhat.com> (raw)
In-Reply-To: <911f42990707310750r349d11c4x9132c68d83cf8cfc@mail.gmail.com>

Jan-Frode Myklebust wrote:
> We run a centralized syslog server, and separate all syslogged avc
> into a separate log file. Is it possible to have setroubleshooter/sealert
> use this log file ?
>
> Also it would be nice if one could get the correct "Host Name" in
> the setroubleshhot browser and alerts. Guess that also will have
> to be added to the avc-log lines is some format.. I tried faking it
> with:
>
> type=AVC msg=audit(1185725759.359:2945): avc:  denied  { search } for
> pid=2077 hostname="my.hostname.com" comm="snmpd" name="fs" dev=proc
> ino=4026531869 scontext=system_u:system_r:snmpd_t:s0
> tcontext=system_u:object_r:sysctl_fs_t:s0 tclass=dir
>
> But the troubleshooter doesn't pick up the hostname. Any ideas ?
>
>
>  -jf
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
>   
If you keep the logs separate you can use sealert on the log files.

sealert -a logfile



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  parent reply	other threads:[~2007-08-02 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 14:50 setroubleshooter/sealert on central loghost? Jan-Frode Myklebust
2007-07-31 18:19 ` Steve G
2007-08-02 14:15 ` Daniel J Walsh [this message]
2007-08-05 20:57   ` Jan-Frode Myklebust
2007-08-06  0:36     ` Steve G

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=46B1E719.500@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=janfrode@tanso.net \
    --cc=selinux@tycho.nsa.gov \
    /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.