Your message dated Tue, 11 Mar 2008 13:52:04 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: this bug/#401761 - libpam-mount makes cron segfault
has caused the Debian Bug report #401761,
regarding libpam-mount makes cron segfault
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(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.)
--
401761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401761
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-87
libpam-mount makes cron segfault each time it forks off a child to run
tasks if it's built with pam support.
strace -f cron -f shows
[pid 3298] setrlimit(RLIMIT_AS, {rlim_cur=RLIM_INFINITY,
rlim_max=RLIM_INFINITY}) = 0
[pid 3298] setrlimit(RLIMIT_LOCKS, {rlim_cur=RLIM_INFINITY,
rlim_max=RLIM_INFINITY}) = 0
[pid 3298] setrlimit(RLIMIT_SIGPENDING, {rlim_cur=RLIM_INFINITY,
rlim_max=RLIM_INFINITY}) = 0
[pid 3298] setrlimit(RLIMIT_MSGQUEUE, {rlim_cur=RLIM_INFINITY,
rlim_max=RLIM_INFINITY}) = 0
[pid 3298] setpriority(PRIO_PROCESS, 0, 0) = 0
[pid 3298] write(2, "pam_mount: error trying to retrieve authtok from auth
code\n", 59pam_mount: error trying to retrieve authtok from auth code
) = 59
[pid 3298] time([1165283281]) = 1165283281
[pid 3298] stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1017, ...})
= 0
[pid 3298] stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1017, ...})
= 0
[pid 3298] stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1017, ...})
= 0
[pid 3298] send(7, "<83>Dec 4 17:48:01 CRON-DEBUG-G[3298]: pam_mount: error
trying to retrieve authtok from auth code\n", 99, MSG_NOSIGNAL) = 99
[pid 3298] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 3298 detached
The problem is indeed linked to:
> polgara [mc]$ cat /etc/pam.d/common-auth
> auth sufficient pam_unix.so
> auth optional pam_mount.so use_first_pass
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> auth sufficient pam_krb5.so retain_after_close forwardable
> refresh_creds use_first_pass
> auth required pam_deny.so
I can move this in all the necessary pam files and remove it from
common-auth so that it's not sourced in /etc/pam.d/cron, but it shouldn't
cause cron to crash.
I can't quite decide if I should file a bug with libpam-mount if it violates
the pam API
with its output, or with cron for the segv
What's your take on this?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
--- End Message ---
--- Begin Message ---
Am Samstag, 8. März 2008 19:55:34 schrieb Justin Pryzby:
> #401761 - libpam-mount makes cron segfault
> http://bugs.debian.org./401761
>
> This bug can be closed now, no?
I think it can be closed. If people still have problems they can file a new
report against the newer version of cron/libpam-mount.
Regards,
Bastian
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
