From: Tony Jones <tonyj@suse.de>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: /sbin/auditd and GSS (was: audit 1.7.6 released)
Date: Thu, 25 Sep 2008 12:12:46 -0700 [thread overview]
Message-ID: <20080925191246.GA9387@suse.de> (raw)
In-Reply-To: <200809131432.54670.sgrubb@redhat.com>
On Sat, Sep 13, 2008 at 02:32:54PM -0400, Steve Grubb wrote:
> On Thursday 11 September 2008 19:39:27 Steve Grubb wrote:
> > I've just released a new version of the audit daemon.
>
> There will be a 1.7.7 release early next week. It will include the GSSAPI
> patch sent yesterday and a fix to a tcp_wrappers problem reported today. Code
> review of GSSAPI support shows that we may need to make a couple more changes
> to it before people start widely deploying it. This should all be taken care
> of in 1.7.7 which I am hoping to be able to release soon.
When I try to build here at SuSE our buildsystem flags the following:
binary /sbin/auditd is linked against libraries in /usr or /opt
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0xb7f65000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0xb7d75000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0xb7d50000)
libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0xb7d43000)
You mentioned (on IRC) rsyslog being another /sbin executable which made use
of GSS but (at least for the package I had access to) the GSS dependancies are
isolated to the rsyslog-module-gssapi module. Modules are loaded by rsyslog
based on configuration file using dlopen().
Clearly this is a bit smoke-n-mirror ish but the direct ldd depenancy between
auditd and GSS is kinda problematic. I assume GSS resides in /usr/lib for
Fedora/RHEL too? Clearly one don't have to configure GSS support in.
Appreciate any comments.
Tony
prev parent reply other threads:[~2008-09-25 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 23:39 audit 1.7.6 released Steve Grubb
2008-09-13 18:32 ` Steve Grubb
2008-09-25 19:12 ` Tony Jones [this message]
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=20080925191246.GA9387@suse.de \
--to=tonyj@suse.de \
--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