Susmit Sarkar created SSHD-1203:
-----------------------------------

             Summary: [[ssh-dss]] none of the keys appears in supported list
                 Key: SSHD-1203
                 URL: https://issues.apache.org/jira/browse/SSHD-1203
             Project: MINA SSHD
          Issue Type: Bug
    Affects Versions: 2.7.0
            Reporter: Susmit Sarkar
             Fix For: 2.7.0


Getting the below exception trace:

30 Jul 2021 17:03:50,834 [sshd-SshServer[2bcef5ca](port=22091)-nio2-thread-2] 
DEBUG ServerSessionImpl  - 
resolveEmptySignaturesProposal(ServerSessionImpl[null@/127.0.0.1:36117])*[[ssh-dss]]
 none of the keys appears in supported list: 
[[email protected], 
[email protected], 
[email protected], [email protected], 
[email protected], ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, 
ecdsa-sha2-nistp521, [email protected], rsa-sha2-512, 
rsa-sha2-256, ssh-rsa]*30 Jul 2021 17:03:50,834 
[sshd-SshServer[2bcef5ca](port=22091)-nio2-thread-2] DEBUG ServerSessionImpl  - 
resolveEmptySignaturesProposal(ServerSessionImpl[null@/127.0.0.1:36117])[[ssh-dss]]
 none of the keys appears in supported list: 
[[email protected], 
[email protected], 
[email protected], [email protected], 
[email protected], ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, 
ecdsa-sha2-nistp521, [email protected], rsa-sha2-512, 
rsa-sha2-256, ssh-rsa]30 Jul 2021 17:03:50,857 
[sshd-SshServer[2bcef5ca](port=22091)-nio2-thread-2] DEBUG Nio2Session  - 
handleReadCycleFailure(Nio2Session[local=/127.0.0.1:22091, 
remote=/127.0.0.1:36117]) SshException after 43009671 nanos at read cycle=1: 
sendKexInit() no resolved signatures available30 Jul 2021 17:03:50,857 
[sshd-SshServer[2bcef5ca](port=22091)-nio2-thread-2] DEBUG Nio2Session  - 
exceptionCaught(Nio2Session[local=/127.0.0.1:22091, remote=/127.0.0.1:36117]) 
caught SshException[sendKexInit() no resolved signatures available] - calling 
handler30 Jul 2021 17:03:50,857 
[sshd-SshServer[2bcef5ca](port=22091)-nio2-thread-2] WARN  ServerSessionImpl  - 
exceptionCaught(ServerSessionImpl[null@/127.0.0.1:36117])[state=Opened] 
SshException: sendKexInit() no resolved signatures 
availableorg.apache.sshd.common.SshException: sendKexInit() no resolved 
signatures available at 
org.apache.sshd.common.session.helpers.AbstractSession.sendKexInit(AbstractSession.java:2281)
 at 
org.apache.sshd.server.session.AbstractServerSession.readIdentification(AbstractServerSession.java:500)
 at 
org.apache.sshd.common.session.helpers.AbstractSession.messageReceived(AbstractSession.java:383)
 at 
org.apache.sshd.common.session.helpers.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:64)
 at 
org.apache.sshd.common.io.nio2.Nio2Session.handleReadCycleCompletion(Nio2Session.java:359)
 at 
org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:336) 
at 
org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:333) 
at 
org.apache.sshd.common.io.nio2.Nio2CompletionHandler.lambda$completed$0(Nio2CompletionHandler.java:38)
 at 
org.apache.sshd.common.io.nio2.Nio2CompletionHandler$$Lambda$913/0000000088B4A540.run(Unknown
 Source) at 
java.security.AccessController.doPrivileged(AccessController.java:678) at 
org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:37)
 at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:138) at 
sun.nio.ch.Invoker$2.run(Invoker.java:230) at 
sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:124)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) 
at java.lang.Thread.run(Thread.java:822)

Post upgrade we are seeing this error, looks like ssh-dss is deprecated in 
2.7.0 but was present in 2.5.1. Can you please help to solve this issue, where 
should we add dss support from code?

 

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]

Reply via email to