[ 
https://issues.apache.org/jira/browse/SSHD-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304414#comment-17304414
 ] 

Thomas Wolf commented on SSHD-1105:
-----------------------------------

This is the root cause of Eclipse bug 
[572056|https://bugs.eclipse.org/bugs/show_bug.cgi?id=572056]: connecting via 
SSH to bitbucket.org git repositories using an RSA key is no longer possible. 
bitbucket.org knows only ssh-rsa, but not rsa-sha2-512. It also doesn't send a 
SSH2_MSG_EXT_INFO server-sig-algs.

(Github does send server-sig-algs, and does understand rsa-sha2-512. So no 
problem there.)

> Use all possible signatures for a public key type in public key authentication
> ------------------------------------------------------------------------------
>
>                 Key: SSHD-1105
>                 URL: https://issues.apache.org/jira/browse/SSHD-1105
>             Project: MINA SSHD
>          Issue Type: Improvement
>    Affects Versions: 2.5.1
>            Reporter: Lyor Goldstein
>            Priority: Minor
>
> The current code iterates over the keys the user provided and then attempts 
> to find a +single+ matching signature factory.  However, for some key types 
> (e.g., RSA) there is more than one possible signature - e.g., {{ssh-rsa, 
> rsa-sha2-256, rsa-sha2-512}}. The code should try +all+ matching signature 
> factories in the same +order+ as the user defined them.
> {code:java|title=Pseudo code}
> for (KeyPair kp : userKeys) {
>     Collection<String> aliases = KeyUtils.getAllKeyTypeAliases(kp);
>     for (SignatureFactory factory : userSignatures) {
>           // NOTE: need to check how not to confuse ...-cert@openssh,com.. 
> key type aliases
>           if (aliases.contains(factory.getName()) {
>                tryPublicKeyAuth(factory, kp);
>           }
>     }
> }
> {code}



--
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