Subject: Re: Login failure with libssh2-1.2.2 and SuSE Enterprise 10 Linux

Re: Login failure with libssh2-1.2.2 and SuSE Enterprise 10 Linux

From: Dave McCaldon <davem_at_intersystems.com>
Date: Mon, 14 Dec 2009 18:33:37 -0500

On Dec 14, 2009, at 5:44 PM, Daniel Stenberg wrote:

> On Mon, 14 Dec 2009, Dave McCaldon wrote:
>
>> => libssh2_transport_read() plain (36 bytes)
>> 0000: 33 00 00 00 1e 70 75 62 6c 69 63 6b 65 79 2c 6b 3....publickey,k
>> 0010: 65 79 62 6f 61 72 64 2d 69 6e 74 65 72 61 63 74 eyboard-interact
>> 0020: 69 76 65 00 ive.
>> [libssh2] 1.264919 Transport: Packet type 51 received, length=36
>> [libssh2] 1.264925 Transport: Looking for packet of type: 52
>> [libssh2] 1.264929 Transport: Looking for packet of type: 51
>
> When we tracked the similar problem with the publickey auth we had lots of help from checking the log in the server side together with libssh2's traces, so I would recommend that you check those out for this as well!

I think I've found the problem. It seems we're asking for an ssh-connection method "password" and this server doesn't seem to allow password. Note that regular [OpenSSH] ssh asks for keyboard-interactive.

debug1: userauth-request for user davem service ssh-connection method password
debug1: attempt 0 failures 0
debug3: mm_getpwnamallow entering
debug3: mm_request_send entering: type 6
debug3: mm_getpwnamallow: waiting for MONITOR_ANS_PWNAM
debug3: mm_request_receive_expect entering: type 7
debug3: mm_request_receive entering
debug3: monitor_read: checking request 6
debug3: mm_answer_pwnamallow
debug3: mm_answer_pwnamallow: sending MONITOR_ANS_PWNAM: 1
debug3: mm_request_send entering: type 7
debug2: monitor_read: 6 used once, disabling now
debug3: mm_request_receive entering
debug2: input_userauth_request: setting up authctxt for davem
debug3: mm_start_pam entering
debug3: mm_request_send entering: type 45
debug3: mm_inform_authserv entering
debug3: mm_request_send entering: type 3
debug2: Unrecognized authentication method name: password

The application code isn't designed to be "driven" by a user, so keyboard-interactive didn't seem the right function to use. The question is, is this just a sshd configuration problem? Or should I be using libssh2_userauth_keyboard_interactive_ex() and then writing a callback function that simply returns the password as supplied by the app?

Many thanks!

_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2009-12-15