well, in fact, it's far from "fix released". I forgot that I blacklisted the message in logcheck because it basically made logcheck too verbose for so long (defeating its "alerting" purpose).
It's still happening a lot in Natty:
$ zgrep -ch "PAM adding faulty module: pam_cap.so" /var/log/auth.log 79
/var/log/messages: Mar 28 17:03:09 srv authdaemond: pam_sm_authenticate: Called Mar 28 17:03:09 srv authdaemond: pam_sm_authenticate: username = [fta]
/var/log/auth.log: Mar 28 17:03:09 srv authdaemond: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: undefined symbol: pam_get_item Mar 28 17:03:09 srv authdaemond: PAM adding faulty module: pam_cap.so
/var/log/syslog: Mar 28 17:03:07 srv imapd-ssl: Connection, ip=[::ffff:x.y.z.t] Mar 28 17:03:09 srv authdaemond: pam_sm_authenticate: Called Mar 28 17:03:09 srv authdaemond: pam_sm_authenticate: username = [fta] Mar 28 17:03:09 srv imapd-ssl: LOGIN, user=fta, ip=[::ffff:x.y.z.t], port=[tttt], protocol=IMAP
of course, my IMAPs works fine.
well, in fact, it's far from "fix released". I forgot that I blacklisted the message in logcheck because it basically made logcheck too verbose for so long (defeating its "alerting" purpose).
It's still happening a lot in Natty:
$ zgrep -ch "PAM adding faulty module: pam_cap.so" /var/log/auth.log
79
/var/log/messages: authenticate: Called authenticate: username = [fta]
Mar 28 17:03:09 srv authdaemond: pam_sm_
Mar 28 17:03:09 srv authdaemond: pam_sm_
/var/log/auth.log: pam_cap. so: undefined symbol: pam_get_item
Mar 28 17:03:09 srv authdaemond: PAM unable to dlopen(pam_cap.so): /lib/security/
Mar 28 17:03:09 srv authdaemond: PAM adding faulty module: pam_cap.so
/var/log/syslog: authenticate: Called authenticate: username = [fta] x.y.z.t] , port=[tttt], protocol=IMAP
Mar 28 17:03:07 srv imapd-ssl: Connection, ip=[::ffff:x.y.z.t]
Mar 28 17:03:09 srv authdaemond: pam_sm_
Mar 28 17:03:09 srv authdaemond: pam_sm_
Mar 28 17:03:09 srv imapd-ssl: LOGIN, user=fta, ip=[::ffff:
of course, my IMAPs works fine.