Dear Maintainer,
* What led up to the situation?
We, for historical reasons (laziness) use UUCP for some inter machine communications
* What exactly did you do (or not do) that was effective (or
ineffective)?
Installed trixie
* What was the outcome of this action?
From time to time in.uucpd crashes, apparently in pam_vprompt ()
* What outcome did you expect instead?
No crashes?
It doesn't crash every time, the majority of calls work.
gdb gives me this backtrace:
Core was generated by `/usr/sbin/in.uucpd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000558463adea07 in ?? ()
(gdb) bt
#0 0x0000558463adea07 in ?? ()
#1 0x00007ffa24f0c590 in pam_vprompt () from /lib/x86_64-linux-gnu/libpam.so.0
#2 0x00007ffa24f0c7ce in pam_prompt () from /lib/x86_64-linux-gnu/libpam.so.0
#3 0x00007ffa24f06b07 in ?? () from /lib/x86_64-linux-gnu/libpam.so.0
#4 0x00007ffa24c5303a in pam_sm_authenticate ()
from /usr/lib/x86_64-linux-gnu/security/pam_unix.so
#5 0x00007ffa24f054de in ?? () from /lib/x86_64-linux-gnu/libpam.so.0
#6 0x00007ffa24f04be3 in pam_authenticate ()
from /lib/x86_64-linux-gnu/libpam.so.0
#7 0x0000558463ade582 in ?? ()
#8 0x00007ffa24d31ca8 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#9 0x00007ffa24d31d65 in __libc_start_main ()
from /lib/x86_64-linux-gnu/libc.so.6
#10 0x0000558463ade901 in ?? ()
(gdb)
No other process on the server is crashing.