public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: excluding auditd events
Date: Thu, 26 May 2011 15:23:09 +0100	[thread overview]
Message-ID: <4DDE624D.6010405@googlemail.com> (raw)
In-Reply-To: <201105261016.13760.sgrubb@redhat.com>


> Sort of. We have kerberos support, but its not enabled at the moment. The reason being 
> is that the kerberos libraries were in /usr/lib64 which is a big problem if the audit 
> system started before the nfs components (and it does). I think the kerberos libraries 
> might have been moved so we could potentially turn that on sometime soon - but I have 
> not been updating or testing the code. If you build your own packages, you can turn it 
> on now. 
>   
Thanks, I'll try as soon as I am able to build a decent version of the 
daemon (as I already pointed out - the show-stopper for me is the older 
version of perl on my FC13 system, which, from what I remember, is a 
dependency for building the remote-logging part of the daemon). When I 
get more confident about understanding the audit daemon better (and 
having looked properly in the code itself) I may come up with few other 
ideas.

  reply	other threads:[~2011-05-26 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  0:22 excluding auditd events Mr Dash Four
     [not found] ` <201105260802.21606.sgrubb@redhat.com>
2011-05-26 13:16   ` Mr Dash Four
2011-05-26 13:50     ` Steve Grubb
2011-05-26 14:07       ` Mr Dash Four
2011-05-26 14:16         ` Steve Grubb
2011-05-26 14:23           ` Mr Dash Four [this message]
2011-05-26 14:33             ` Steve Grubb
2011-05-26 15:22               ` Mr Dash Four
2011-05-26 15:51                 ` LC Bruzenak
2011-05-26 16:10                   ` Mr Dash Four
2011-06-01 12:54           ` Mr Dash Four
2011-06-01 14:08             ` LC Bruzenak
2011-06-01 14:47               ` Mr Dash Four

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=4DDE624D.6010405@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@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