[
https://issues.apache.org/jira/browse/SSHD-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046642#comment-15046642
]
Goldstein Lyor commented on SSHD-474:
-------------------------------------
The problem is indeed when first KEX packet follows which requires ignore. None
of the current SSH clients use this option so we have not had to contend with
it. I am testing some code that is designed to overcome this issue, and it does
to the extent of getting over this bump. However, some other packets down the
road after successful key establishment become corrupted (at least when using
_DropBear_). We need a deeper understanding of what this means.
> Null pointer exception when connecting with latest Dropbear's dbclient
> ----------------------------------------------------------------------
>
> Key: SSHD-474
> URL: https://issues.apache.org/jira/browse/SSHD-474
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 0.14.0
> Environment: Apache SSHD 0.14.0 binary distribution on a Redhat 6
> system. Oracle Java 1.7.0_25. Dropbear 2015.67.
> Reporter: Andrew Danforth
> Priority: Minor
> Attachments: dbclient.log, sshd.log
>
>
> SSHD throws a null pointer exception when using dbclient from Dropbear
> 2015.67 to connect. I believe this is due to dbclient attempting to reduce
> message exchange during key negotiation. If you compile dbclient and comment
> out #define USE_KEX_FIRST_FOLLOWS from sysoptions.h the session proceeds as
> expected. FWIW, this version of dbclient has no issues interacting with an
> OpenSSH daemon.
> I will attach a log of the SSHD output as well as the shell command to start
> dbclient.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
