[email protected]
[Top] [All Lists]

Bug#472986: marked as forwarded (libpam-p11 should use pam_syslog for lo

Subject: Bug#472986: marked as forwarded libpam-p11 should use pam_syslog for logging instead of openlog/syslog/closelog
From: Debian Bug Tracking System
Date: Sat, 26 Apr 2008 05:24:05 +0000
Your message dated Sat, 26 Apr 2008 01:22:25 -0400
with message-id <[email protected]>
has caused the   report #472986,
regarding libpam-p11 should use pam_syslog for logging instead of 
openlog/syslog/closelog
to be marked as having been forwarded to the upstream software
author(s) [email protected]

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
472986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472986
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: (forw) Re: Bug#472986: [SPAM?] Re: Bug#472986: /bin/su: su segfaults with libpam-p11 activated in /etc/pam.d/common-auth
From: Eric Dorland
Date: Sat, 26 Apr 2008 01:22:25 -0400
Hello opensc type persons,

A Debian user has discovered a bug in pam_p11. It uses the syslog
family of functions instead of pam_syslog, which causes segfaults in
some situations. Please apply the attached patch!

-- 
Eric Dorland <[email protected]>
ICQ: #61138586, Jabber: [email protected]

--- Begin Message ---
Subject: Re: Bug#472986: [SPAM?] Re: Bug#472986: /bin/su: su segfaults with libpam-p11 activated in /etc/pam.d/common-auth
From: Nicolas François
Date: Tue, 15 Apr 2008 02:47:07 +0200
reassign 472986 libpam-p11
retitle 472986 libpam-p11 should use pam_syslog for logging instead of 
openlog/syslog/closelog
notfound 472986 1:4.1.0-2
found 472986 0.1.3-1
thanks


Hello,

libpam-p11 uses openlog/syslog/closelog sequences.

The closelog calls will break applications if they wish to report logs
after calling pam functions.

In the case of the original segfault in su, the issue was caused by
openlog. I don't really understand why it is problematic to openlog()
twice, but the attached patch fixed the segfault is su.

pam_syslog will also make the syslog message look prettier (it will
mention the service, not only the name of the module).

Best Regards,
-- 
Nekral

Attachment: libpam-p11_no_openlog.patch
Description: Text Data


--- End Message ---

--- End Message ---
<Prev in Thread] Current Thread [Next in Thread>
  • Bug#472986: marked as forwarded (libpam-p11 should use pam_syslog for logging instead of openlog/syslog/closelog), Debian Bug Tracking System <=