www.libssh2.org | Daily snapshots | Mailing list archive | Docs | Examples | github

Archive Index This month's Index

Subject: Re: Authentication issue

Re: Authentication issue

From: Dan Fandrich <dan_at_coneharvesters.com>
Date: Sat, 25 Jul 2015 13:46:30 +0200

On Tue, Jul 21, 2015 at 12:21:41PM +0530, Kishore Av wrote:
> Thanks Dan, -v options really helps me to check debug.
>
> Authentication success, got confirmed by libssh2_userauth_authenticated.
> Channel created success.
>
> Now there is another issue,
> while executing command It's returning error string "Failed waiting for channel
> success".
>
> May I know what problem it is???

That error message comes from the function _libssh2_channel_process_startup.
It occurs when the reply code SSH_MSG_CHANNEL_SUCCESS or
SSH_MSG_CHANNEL_FAILURE are not received. The error code printed in that error
message will give you a better idea why that might be the case.

>>> Dan

>
> Thanks
> Kishore
>
> On 21-Jul-2015 3:08 am, "Dan Fandrich" <dan_at_coneharvesters.com> wrote:
>
> On Fri, Jul 17, 2015 at 04:18:06PM +0530, Kishore Av wrote:
> > Thanks for response,
> > I already tried userauth_list and it returns NULL.
> > Based on your explanation i comes to know that, ssh server should be
> configured
> > as none. It seems server issue.
>
> While it may appear that 'ssh <IP address>' is connecting without
> authentication, there are several ways that ssh could be silently
> authenticating without requiring a password and without you realizing it
> (e.g.
> Kerberos, private key, ssh-agent). If you give the -v option on the OpenSSH
> client command-line, it will show you the steps it is going to authenticate
> the
> connection.  There's a good chance that it's not actually unauthenticated.
> In
> today's world, there are few instances where that's a good idea.
>
> >
> > Thanks
> > Kishore
> >
> > On 17-Jul-2015 2:47 pm, "Peter Stuge" <peter_at_stuge.se> wrote:
> >
> >     Kishore Av wrote:
> >     > I could able to connect ssh server only with username and without
> >     > providing the password manually.
> >
> >     Did you study the protocol specification?
> >
> >     RFC 4252 5.2.  The "none" Authentication Request
> >
> >        A client may request a list of authentication 'method name' values
> >        that may continue by using the "none" authentication 'method
> name'.
> >
> >
> >     > Is there a way to connect that server through libssh2 ?
> >
> >     As I wrote, the libssh2 API matches the protocol API closely.
> >
> >
> >     > If so, which API can be used to connect?
> >
> >     Did you study the library API documentation?
> >
> >     /* libssh2_userauth_list
> >      *
> >      * List authentication methods
> >      * Will yield successful login if "none" happens to be allowable for
> this
> >     user
> >
> >
> >
> >     //Peter
> >     _______________________________________________
> >     libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/
> libssh2-devel
> >
>
> > _______________________________________________
> > libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
>
> _______________________________________________
> libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
>

> _______________________________________________
> libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel

_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2015-07-25

the libssh2 team