From: Steve Grubb <sgrubb@redhat.com>
To: Mr Dash Four <mr.dash.four@googlemail.com>
Cc: linux-audit@redhat.com
Subject: Re: excluding auditd events
Date: Thu, 26 May 2011 10:16:13 -0400 [thread overview]
Message-ID: <201105261016.13760.sgrubb@redhat.com> (raw)
In-Reply-To: <4DDE5EBD.7060601@googlemail.com>
On Thursday, May 26, 2011 10:07:57 AM Mr Dash Four wrote:
> > For ultimate protection, we suggest remote logging to a box that has
> > restricted access.
>
> That is certainly a possibility (but then again the box needs to be
> "secure"), though since I am not very familiar with the audit daemon
> I'll just ask - is the connection between the 2 daemons (on the secure
> box as well as the daemon sending the logs) encrypted so to prevent
> tampering in-route (man in the middle etc attacks)?
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.
-Steve
next prev parent reply other threads:[~2011-05-26 14:16 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 [this message]
2011-05-26 14:23 ` Mr Dash Four
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=201105261016.13760.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=mr.dash.four@googlemail.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.