Re: Failed Password Error

From: Darren Tucker (dtucker_at_dodgy.net.au)
Date: 12/21/03 

Date: Sun, 21 Dec 2003 02:45:04 +0000 (UTC)

In article <r60auv8rp2v9ik624fops3imu6gcmj2me9@4ax.com>,
Mark Olbert <mark@arcabama.com> wrote:
[snip]
>Dec 20 18:10:27 pixel sshd[20153]: debug2: monitor_read: 3 used once, disabling now
>Dec 20 18:10:27 pixel sshd[20153]: debug3: mm_request_receive entering
>Dec 20 18:10:31 pixel sshd[20153]: debug1: Calling cleanup 0x8060f70(0x0)
>Dec 20 18:10:31 pixel sshd[20153]: debug1: PAM: cleanup
>
>Any other suggestions?

It's possible that the PAM authentication thread is crashing for some
reason. You could try running sshd under a debugger. Make sure you
have UsePAM=yes, PasswordAuthentication=no and
ChallengeResponseAuthentication=yes in sshd_config, then:

# gdb ./sshd
(gdb) set args -ddd -p 2022 -o UsePrivilegeSeparation=no
(gdb) set follow-fork child
(gdb) run

then connect to port 2022. If it returns to the gdb prompt, do "bt"
to get a stack trace.

What kind of system (ie OS) is this? I'd guess a Linux based on the
location of the PAM file. Which PAM modules are you using?

BTW, the PAM authentication code in 3.7p1 was replaced and now does
keyboard-interactive rather than password authentication. 

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.