Package: libpam-runtime
Version: 1.0.1-7
Severity: normal
File: /usr/sbin/pam-auth-update
While writing the 'namespace' pam-auth-update configuration file Emacs created
/usr/share/pam-config/namespace~ as a backup file. The file 'namespaces~'
also existed (note the extra 's') in the configuration directory.[1]
When I ran pam-auth-update to enable my new configuration I was presented with
two 'namespace' definitions; it seems that the tool parsed the content twice.
I don't know which of the two files was picked up twice, sorry.
It would be sensible, I think, to define a standard suffix for the
configuration files (eg: .conf) and use that as a "whitelist" for valid files,
since that will ensure that *only* valid configuration files are loaded.
Alternately, you may need to extend the blacklist of files to ignore, although
I think that is a loosing battle myself. :)
Regards,
Daniel
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libpam-runtime depends on:
ii debconf 1.5.26 Debian configuration management sy
libpam-runtime recommends no packages.
libpam-runtime suggests no packages.
-- debconf information:
libpam-runtime/conflicts:
libpam-runtime/override: false
libpam-runtime/profiles: unix, namespace, consolekit
Footnotes:
[1] I renamed the configuration file to match the PAM module name.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
