[
https://issues.apache.org/jira/browse/SSHD-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373409#comment-15373409
]
Goldstein Lyor commented on SSHD-673:
-------------------------------------
The problem is several fold:
1. Since no key size specified, BouncyCastle generates a non-standard EC key
(239 bits)
2. There is currently no support for specifying a preferred key size via the
command line
3. The reported algorithm for the BouncyCastle generated key is "ECDSA" instead
of the standard "EC" (though "EC" is the requested one).
I have fixed these issues and they will be available in next release. You can
work around this problem if you write your own server code - look at
{{SshServer#main}} and see it is relatively simple. You can also look at the
changes I have made and do something similar (at least by setting the key size).
> "sendKexInit() no resolved signatures available" with key-type "EC"
> -------------------------------------------------------------------
>
> Key: SSHD-673
> URL: https://issues.apache.org/jira/browse/SSHD-673
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 1.2.0
> Environment: Arch Linux
> openssh 7.2p2
> OpenSSL 1.0.2h 3 May 2016
> org.bouncycastle:bcprov-jdk15on:1.54
> Oracle JDK 1.7.0_80
> Reporter: Benedikt Waldvogel
> Assignee: Goldstein Lyor
>
> Steps to reproduce:
> # {{java org.apache.sshd.server.SshServer -p 1234 -key-type EC}}
> # {{ssh -vv -p 1234 localhost}}
> {noformat}
> > OpenSSH_7.2p2, OpenSSL 1.0.2h 3 May 2016
> > …
> > debug1: Remote protocol version 2.0, remote software version SSHD-CORE-1.2.0
> > …
> > debug1: SSH2_MSG_KEXINIT sent
> > Received disconnect from ::1 port 1234:9: sendKexInit() no resolved
> > signatures available
> > Disconnected from ::1 port 1234
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
