You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Susmit Sarkar (Jira)" <ji...@apache.org> on 2021/07/27 13:22:00 UTC
[jira] [Comment Edited] (SSHD-1201) Sever Keys name wrong post
upgrade to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388025#comment-17388025 ]
Susmit Sarkar edited comment on SSHD-1201 at 7/27/21, 1:21 PM:
---------------------------------------------------------------
[~gnodet] in my case its *ssh-rsa* but the API is returning *rsa-sha2-512,* so you think the same fix will address the issue
when serverKey is "ssh-rsa" it only returns *"rsa-sha2-512"*
was (Author: susmit07):
[~gnodet] in my case its *ssh-rsa* but the API is returning *rsa-sha2-512,* so you feel the same fix will address the issue
when serverKey is "ssh-rsa" it only returns *"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
> Fix For: 2.7.0
>
>
> 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: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org