Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

DCB: SshException "EdDSA provider not supported"

Description

From the OpenNMS Karaf logs:

 

From , this link may be relevant:

https://stackoverflow.com/questions/65566138/apache-mina-sshd-ssh-client-always-prints-eddsa-provider-not-supported

 

was aware of this cipher suite missing from our SSH client stack, it's a matter of adding a library to get it working, but there have been some challenges to date.

Environment

DCB sponsor network, backing up a Juniper EX2300 switch running Junos 20.4R3-S1.3

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

JianYet August 31, 2023 at 8:49 PM

can you look into ? If need be, reopen this ticket or I can open a new one.

Chandra Gorantla May 25, 2022 at 7:56 PM
Edited

This was indeed warning not an error.
Tried this at customer end and we didn't encouter any issues while backing up the config.

I tried to include net.i2p.crypto/eddsa library but i was not able to get this working within karaf. Karaf has a boot feature ssh and this feature doesn't include net.i2p.crypto/eddsa. May be we need to overwrite this boot feature.

Since customer doesn't need eddsa on their setup, we can close this for now.

Chandra Gorantla May 17, 2022 at 11:07 PM
Edited

Tried this with same docker-compose file that was used to setup customer environment.
And this failed to retrieve device config from the juniper vm. From logs, it looks like juniper vm couldn't reach the docker network ip ( 172.18.0.3).

Then tried with network_mode: host on the docker and everything worked fine.

I suspect docker networking may be the real problem here.

Chandra Gorantla May 17, 2022 at 5:29 PM

Good news :
I tried this by running OpenNMS in linux environment, I see similar warning but SSH connection and config retrieval was successful.

Bad news:
we don't know what is causing the issue.

Next steps:
try reproducing the problem in docker environment

Jeff Gehlbach May 17, 2022 at 5:07 PM

For whatever it's worth, here is the heavily-redacted config of the monitored device against which we saw this problem.

Not a Bug

Details

Assignee

Reporter

Labels

Sprint

Fix versions

Affects versions

Priority

Parent

PagerDuty

Created May 17, 2022 at 1:52 PM
Updated September 12, 2023 at 3:58 PM
Resolved May 25, 2022 at 8:06 PM