Yingfang Chen created SSHD-1159:
-----------------------------------

             Summary: Client:Sent SSH_MSG_USERAUTH_REQUEST twice even 
PASSWORD_PROMPTS=1
                 Key: SSHD-1159
                 URL: https://issues.apache.org/jira/browse/SSHD-1159
             Project: MINA SSHD
          Issue Type: Bug
    Affects Versions: 2.2.0
         Environment: SSHD version:2.2.0
Java version:openjdk version "11.0.7" 2020-04-14
            Reporter: Yingfang Chen
             Fix For: 2.2.0
         Attachments: log_sent_to_apache_ssh.txt

Keyboard-interactive authentication sent SSH_MSG_USERAUTH_REQUEST twice even 
though we set SshClient 
ClientAuthenticationManager.{color:#9876aa}PASSWORD_PROMPTS 
{color}{color:#172b4d}to 1{color}{color:#9876aa}
{color}

{color:#172b4d}Here is console output from ssh command line client. Incorrect 
password is provided
{color}{color:#172b4d}$ssh -vv -o PreferredAuthentications=keyboard-interactive 
-o NumberOfPasswordPrompts=1 user@localhost{color}

...

debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
_some banner_

debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug2: input_userauth_info_req
debug2: input_userauth_info_req: num_prompts 1
Password: 
{color:#de350b}debug1: Authentications that can continue: 
publickey,keyboard-interactive{color}
{color:#de350b}debug2: we did not send a packet, disable method{color}
{color:#de350b}debug1: No more authentication methods to try.{color}
localhost: Permission denied (publickey,keyboard-interactive).

But in UserAuthenticationManager.java, another SSH_MSG_USERAUTH_REQUEST was 
send before processing SSH_MSG_USERAUTH_FAILURE.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to