Re: Failed Password Error

From: Mark Olbert (mark_at_arcabama.com)
Date: 12/21/03 

Date: Sat, 20 Dec 2003 18:10:09 -0800

No joy, it still doesn't work. Here's the DEBUG3 log:

Dec 20 18:10:22 pixel sshd[20151]: debug1: Forked child 20153.
Dec 20 18:10:22 pixel sshd[20153]: Connection from 172.196.97.167 port 1050
Dec 20 18:10:23 pixel sshd[20153]: debug1: Client protocol version 2.0; client software version
PenguiNet-$Re$
Dec 20 18:10:23 pixel sshd[20153]: debug1: no match: PenguiNet-$Revision:_1.49.2.3_$
Dec 20 18:10:23 pixel sshd[20153]: debug1: Enabling compatibility mode for protocol 2.0
Dec 20 18:10:23 pixel sshd[20153]: debug1: Local version string SSH-1.99-OpenSSH_3.7.1p2
Dec 20 18:10:23 pixel sshd[20153]: debug2: Network child is on pid 20154
Dec 20 18:10:23 pixel sshd[20153]: debug3: preauth child monitor started
Dec 20 18:10:23 pixel sshd[20153]: debug3: mm_request_receive entering
Dec 20 18:10:23 pixel sshd[20153]: debug3: monitor_read: checking request 4
Dec 20 18:10:23 pixel sshd[20153]: debug3: mm_answer_sign
Dec 20 18:10:23 pixel sshd[20153]: debug3: mm_answer_sign: signature 0x8109310(143)
Dec 20 18:10:23 pixel sshd[20153]: debug3: mm_request_send entering: type 5
Dec 20 18:10:23 pixel sshd[20153]: debug2: monitor_read: 4 used once, disabling now
Dec 20 18:10:23 pixel sshd[20153]: debug3: mm_request_receive entering
Dec 20 18:10:27 pixel sshd[20153]: debug3: monitor_read: checking request 6
Dec 20 18:10:27 pixel sshd[20153]: debug3: mm_answer_pwnamallow
Dec 20 18:10:27 pixel sshd[20153]: debug3: mm_answer_pwnamallow: sending MONITOR_ANS_PWNAM: 1
Dec 20 18:10:27 pixel sshd[20153]: debug3: mm_request_send entering: type 7
Dec 20 18:10:27 pixel sshd[20153]: debug2: monitor_read: 6 used once, disabling now
Dec 20 18:10:27 pixel sshd[20153]: debug3: mm_request_receive entering
Dec 20 18:10:27 pixel sshd[20153]: debug3: monitor_read: checking request 43
Dec 20 18:10:27 pixel sshd[20153]: debug1: PAM: initializing for "mark"
Dec 20 18:10:27 pixel sshd[20153]: debug3: Trying to reverse map address 172.196.97.167.
Dec 20 18:10:27 pixel sshd[20153]: debug1: PAM: setting PAM_RHOST to "acc461a7.ipt.aol.com"
Dec 20 18:10:27 pixel sshd[20153]: debug1: PAM: setting PAM_TTY to "ssh"
Dec 20 18:10:27 pixel sshd[20153]: debug2: monitor_read: 43 used once, disabling now
Dec 20 18:10:27 pixel sshd[20153]: debug3: mm_request_receive entering
Dec 20 18:10:27 pixel sshd[20153]: debug3: monitor_read: checking request 3
Dec 20 18:10:27 pixel sshd[20153]: debug3: mm_answer_authserv: service=ssh-connection, style=
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?

- Mark

On Sun, 21 Dec 2003 01:27:15 +0000 (UTC), dtucker@dodgy.net.au (Darren Tucker) wrote:

>In article <vej9uvsg6m0ri7j27ddc2u4iaoqq1lvc7i@4ax.com>,
>Mark Olbert <mark@arcabama.com> wrote:
>>I used to be a happy camper... but now that I've upgraded to 3.7p1 I
>>can't connect through my sshd from a remote connection where I always
>>could before.
>
>3.7p1 has a nasty bug in the PAM support and you shouldn't use it.
>http://www.openssh.org/txt/sshpam.adv
>
>>I'm getting the "Failed password for <user>..." problem (I also used to
>>get the "Nasty PTR..." problem, but I fixed that).
>
>With 3.7.1p2, try it with the following in sshd_config:
>UsePAM yes
>PasswordAuthentication no
>ChallengeResponseAuthentication yes