Hi Liang, It is possible that all functionalities do not work in SSH1. Is there a specific reason why you'd need SSH1 ? This protocol is mostly out of date and insecure.
If I find some time I can have a look and see what's missing. Aris Le 3/11/14 18:35, Liang Qin a écrit : > The keyboard interactive is disabled, below is the config on ssh server: > Protocol 1 > SyslogFacility AUTHPRIV > PasswordAuthentication yes > ChallengeResponseAuthentication no > GSSAPIAuthentication yes > GSSAPICleanupCredentials yes > UsePAM yes > AcceptEnv LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE > LC_MONETARY LC_MESSAGES > AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT > AcceptEnv LC_IDENTIFICATION LC_ALL > X11Forwarding yes > Subsystemsftp/usr/libexec/openssh/sftp-server > > > The blocking mode is working with SSH1 though > > On Mon, Nov 3, 2014 at 4:01 AM, Dexter Aparicio <[email protected] > <mailto:[email protected]>> wrote: > > have you check if the ssh server sshd_config is keyboard interactive? > > On Sat, Nov 1, 2014 at 8:08 AM, Liang Qin <[email protected] > <mailto:[email protected]>> wrote: > > I'm using libssh 0.6.3, trying to make it work with > non-blocking mode, but find that it always fail after sending > the username, it seems that function wait_auth1_status dose > not deal with the non-blocking mode well, it always return > SSH_AUTH_ERROR. > > > > > > -- > Liang Qin CISSP |[email protected] <mailto:[email protected]> > Software Engineer > Qualys, Inc. | Continuous Security | www.qualys.com > <http://www.qualys.com/> > <http://www.qualys.com/> > Direct: 650.801.7728 | Fax : 650.801.6149
