Package: libpam0g
Version: 0.76-22
Severity: normal
It appears that I have a PAM configuration file with bad syntax - I am
getting errors like this whenever I run something that uses PAM:
10.0.0.15 su[17187]: PAM adding faulty module: unknown module path*>
10.0.0.15 su[17187]: PAM unable to dlopen(unknown module path*>)
10.0.0.15 su[17187]: PAM [dlerror: unknown module path*>: cannot open shared
object file: No such file or directory]
Looking in the PAM source, it looks like this is coming from
libpam/pam_handlers.c:
#define UNKNOWN_MODULE_PATH "<*unknown module path*>"
...
/* if NULL set to something that can be searched for */
switch (mod_path != NULL) {
default:
...
case 0:
mod_path = UNKNOWN_MODULE_PATH;
}
Since it seems that mod_path shouldn't be null (?), I'd really rather
have this piece of code log an error when it is null, to help me track
down the source of the problem, rather than setting it to a bogus
value which will only cause obscure problems later on. I've spent
quite a while with 'strace' etc. trying to figure out where it is
coming from, with no luck.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (600, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.25-powerpc
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Versions of packages libpam0g depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libpam-runtime 0.76-22 Runtime support for the PAM librar
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
