[
https://issues.apache.org/jira/browse/SSHD-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388320#comment-17388320
]
Thomas Wolf commented on SSHD-1201:
-----------------------------------
The negotiation result depends on the proposals the client and server make
during key exchange. In OpenSSH you have some control over these proposals via
the {{HostKeyAlgorithm}} SSH config; in Apache MINA sshd with the default
client or server it depends on the installed signature factories and on their
order. Users of Apache MINA sshd can implement more elaborate choice mechanisms
on top of that. See for instance method
{{AbstractSession.resolveAvailableSignaturesProposal()}}.
> Sever Keys name wrong post upgrade to 2.7.0
> -------------------------------------------
>
> Key: SSHD-1201
> URL: https://issues.apache.org/jira/browse/SSHD-1201
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Susmit Sarkar
> Priority: Blocker
>
> Hello Team,
> We upgrade to 2.7.0 from 2.5.1
> we are seeing an issue
>
> String hostkey =
> sftpClient.getSession().getNegotiatedKexParameter(KexProposalOption.SERVERKEYS);
>
>
> Host Key in 2.5.1 was *ssh-rsa* and now with the upgrade to 2.7.0 all our
> test cases are failing as the API is returning *rsa-sha2-512*
> Please note the keys were actually created using ssh-rsa using 2.5.1 library
>
> Thanks,
> Susmit
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
