From: Fmy Oen <fmyoen@gmail.com>
To: linux-audit@redhat.com
Subject: Re: missing user authentication events.
Date: Tue, 29 Nov 2011 12:24:32 +0000 (UTC) [thread overview]
Message-ID: <loom.20111129T131946-983@post.gmane.org> (raw)
In-Reply-To: 201003251511.33968.sgrubb@redhat.com
Hi, I have the same problem Robert Harris talking about.
CentOS:
> ldd /lib/libpam.so.0
linux-gate.so.1 => (0x00680000)
libdl.so.2 => /lib/libdl.so.2 (0x00601000)
libaudit.so.0 => /lib/libaudit.so.0 (0x0069a000)
libc.so.6 => /lib/libc.so.6 (0x004a6000)
/lib/ld-linux.so.2 (0x00482000)
> strings /lib/libpam.so.0 | grep audit_open
audit_open
audit_open() failed: %m
Debian:
> ldd /lib/libpam.so.0
linux-gate.so.1 => (0xb7733000)
libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb771c000)
libcrypt.so.1 => /lib/i686/cmov/libcrypt.so.1 (0xb76ea000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb75a3000)
/lib/ld-linux.so.2 (0xb7734000)
> strings /lib/libpam.so.0 | grep audit_open
>
I managed to recompile login package but I'm having problems with compilation of
libpam0g (/lib/libpam.so.0 containing package):
> sudo dpkg-buildpackage -rfakeroot -b
...
/bin/bash ../../libtool --tag=CC --mode=link gcc -I../../libpam/include
-I../../libpamc/include -I../../libpam_misc/include -g -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -O2 -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual
-Wmissing-declarations -Wmissing-prototypes -Wpointer-arith -Wreturn-type
-Wstrict-prototypes -Wwrite-strings -Winline -Wshadow -no-undefined
-avoid-version -module -Wl,--version-script=./../modules.map -Wl,-z,defs
-Wl,--as-needed -Wl,-O1 -o pam_selinux.la -rpath /lib/security pam_selinux.lo
-L../../libpam -lpam -lselinux -lcrypt
libtool: link: gcc -shared .libs/pam_selinux.o -Wl,-rpath
-Wl,/home/fmyoen/tmp/1/pam-1.1.1/libpam/.libs
-L/home/fmyoen/tmp/1/pam-1.1.1/libpam
/home/fmyoen/tmp/1/pam-1.1.1/libpam/.libs/libpam.so -lselinux -lcrypt
-Wl,--version-script=./../modules.map -Wl,-z -Wl,defs -Wl,--as-needed -Wl,-O1
-Wl,-soname -Wl,pam_selinux.so -o .libs/pam_selinux.so
.libs/pam_selinux.o: In function `send_audit_message':
/home/fmyoen/tmp/1/pam-1.1.1/modules/pam_selinux/pam_selinux.c:87: undefined
reference to `audit_open'
/home/fmyoen/tmp/1/pam-1.1.1/modules/pam_selinux/pam_selinux.c:112:
undefined reference to `audit_log_user_message'
collect2: ld returned 1 exit status
make[4]: *** [pam_selinux.la] Error 1
make[4]: Leaving directory `/home/fmyoen/tmp/1/pam-1.1.1/modules/pam_selinux'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/fmyoen/tmp/1/pam-1.1.1/modules'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/fmyoen/tmp/1/pam-1.1.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/fmyoen/tmp/1/pam-1.1.1'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Any ideas what should I do? For me it looks like some packages still need to be
recompiled. How can I trace it?
next prev parent reply other threads:[~2011-11-29 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 15:17 missing user authentication events Robert Harris
2010-03-25 16:09 ` Steve Grubb
2010-03-25 18:36 ` Robert Harris
2010-03-25 19:11 ` Steve Grubb
2011-11-29 12:24 ` Fmy Oen [this message]
2011-11-29 16:17 ` Steve Grubb
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=loom.20111129T131946-983@post.gmane.org \
--to=fmyoen@gmail.com \
--cc=linux-audit@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