[ 
https://issues.apache.org/jira/browse/SSHD-1163?focusedWorklogId=603907&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-603907
 ]

ASF GitHub Bot logged work on SSHD-1163:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/May/21 12:00
            Start Date: 30/May/21 12:00
    Worklog Time Spent: 10m 
      Work Description: smilesometimes edited a comment on pull request #195:
URL: https://github.com/apache/mina-sshd/pull/195#issuecomment-850988381


   HAHHA, I  find this commit , this is a bug .   
   
   At begining  i was wondering  why  the  method of getting keyAlg    in    
org.apache.sshd.client.kex.DHGEXClient#next   and   
org.apache.sshd.client.kex.DHGClient#next was differrent? 
   
   Because the  method KeyUtils.getKeyType(serverKey)  called in DHGEXClient ;  
    when serverKey is "rsa-sha2-256" and  "rsa-sha2-512"  only return "ssh-rsa" 
, this lead to  a  error called  "KeyExchange signature verification failed for 
key type= ssh-rsa". The usege of  DHGClient is right.
   
   I use this way  to bypass、let the "etch" configed before the  
"diffie-hellman-group", so the DHGClient can be userd for kex.
   
   `
   KexAlgorithms = 
**ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521**,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1.
 `
   
   
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 603907)
    Time Spent: 50m  (was: 40m)

> Wrong server key algorithm choose
> ---------------------------------
>
>                 Key: SSHD-1163
>                 URL: https://issues.apache.org/jira/browse/SSHD-1163
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Max Traydakalo
>            Priority: Major
>             Fix For: 2.7.1
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Wrong server key type algorithm choose (in case of use rsa-sha2-256 and 
> rsa-sha2-512 always identify like ssh-rsa) in case of usage DHFactories with 
> group exchange.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to