If you handle SSH_AUTH_AGAIN with a loop, you probably want to use
blocking mode instead. Non-blocking mode is suitable if your application
works asynchronously.
Am 05.05.2017 um 10:47 schrieb Daniel Kroker:
> thanks i try it.
>
> whats the best way to handle SSH_AUTH_AGAIN ? while loop and try
thanks i try it.
whats the best way to handle SSH_AUTH_AGAIN ? while loop and try again
ssh_userauth_none ?
Am 05.05.2017 um 10:32 schrieb Tilo Eckert:
You did not check the return code "rc".
You could already be logged in after the ssh_userauth_none() call (e.g.
IP based auth). An error
Hi,
thanks for your reply. i call ssh_userath_none.
Here is a small snippet from our program:
if(!session)
{
qDebug()<<"Session not established";
qDebug()<<"SSH Error 12:",ssh_get_error(session);
return-1;
}
rc=ssh_userauth_none(session,NULL);
method=ssh_userauth_list(session,NULL);
http://api.libssh.org/stable/group__libssh__auth.html#ga35d44897a44b4bb3b7c01108c1812a37
You either did not call ssh_userauth_none() before or the server does
not allow any of the supported auth methods.
Regards
Tilo
Am 05.05.2017 um 09:26 schrieb Daniel Kroker:
> Hi,
>
> we have the problem
Hi,
we have the problem that in some cases ssh_userauth_list(session,NULL);
returned 0.
What is 0 exacly?
