|
You claim to have implemented keyboard interactive authentication, however I cannot figure out (nor find examples), how it should work - I can see only Authenticate methods requiring a password. |
|
Keyboard authentication still involves a user typing a password to log in to the SSH account. Chilkat handles the keyboard authentication internally. The password is provided as an argument to the AuthenticatePw method, and if keyboard authentication is required by the server, then the Chilkat AuthenticatePw method internally does everything required to complete the authentication. Thanks, however this is not the correct way how to handle keyboard authentication. In our case, server sends a challenge, which the client must process and generate a password based on this challenge. Or do you have another way how to deliver this challenge to the client?
(Oct 24 '12 at 14:11)
chilkat ♦♦
Yes, this is exactly what happens internally. Within AuthenticatePw, the challenge is received, and the response is generated and sent. The whole process happens internal to AuthenticatePw.
(Oct 24 '12 at 14:13)
chilkat ♦♦
|
