[
https://issues.apache.org/jira/browse/SSHD-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Wolf resolved SSHD-1201.
-------------------------------
Fix Version/s: (was: 2.7.0)
Resolution: Not A Problem
This is not a key type but the negotiated signature algorithm name. 2.5.1
didn't have the SHA-2-based signatures for RSA yet, 2.7.0 does.
Before the SHA-2 signatures were introduced, key types and signature algorithm
names were always equal. Since then, the two can be different for RSA keys. For
RSA keys, the negotiated signature algorithm may be "ssh-rsa", "rsa-sha2-256",
or "rsa-sha2-512".
> 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]
