Marc-Christian Petersen wrote: > since upgrade to sudo 1.8.3-1 I get lots of these log entries > in my syslog: > > Oct 24 15:01:31 hostname sudo: PAM pam_set_item: NULL pam handle passed > Oct 24 15:01:31 hostname sudo: PAM pam_setcred: NULL pam handle passed > Oct 24 15:01:31 hostname sudo: PAM pam_open_session: NULL pam handle passed > Oct 24 15:01:31 hostname sudo: PAM pam_end: NULL pam handle passed
I am seeing these too. Downgrading avoids the noise. This error comes from libpam itself when called with a NULL argument. The prototype is: int pam_set_item(pam_handle_t *pamh, int item_type, const void *item); Early in the pam routines there is this check: IF_NO_PAMH("pam_set_item", pamh, PAM_SYSTEM_ERR); Apparently 'pamh' is NULL. Looks like a usage problem. Bob -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org