[
https://issues.apache.org/jira/browse/SSHD-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Wolf closed SSHD-1260.
-----------------------------
Fix Version/s: 2.15.0
Resolution: Fixed
Support for Bouncy Castle ed25519 was added in [Github PR
639|https://github.com/apache/mina-sshd/pull/639]. Users can decide whether or
not they want to use the net.i2p library. If net.i2p.crypto.eddsa is not
present at run-time, Bouncy Castle (if present) will be used for ed25519.
> EdDSA dependency net.i2p.crypto ed25519 signatures are malleable
> ----------------------------------------------------------------
>
> Key: SSHD-1260
> URL: https://issues.apache.org/jira/browse/SSHD-1260
> Project: MINA SSHD
> Issue Type: Dependency upgrade
> Reporter: Dominik Schneider
> Priority: Major
> Fix For: 2.15.0
>
>
> To use ed25519 keys with the SSHD server it is necessary to use the
> net.i2p.crypto dependency. This dependency has a security flaw as it uses
> malleable ed25519 signatures as described in this github
> [issue|[https://github.com/str4d/ed25519-java/issues/82]].
> This issue was detected in the context of a paper which checked several
> ed25519 implementations for security issues. In Table 5 of the paper, they
> state that this dependency is not SUF-CMA compliant in contrast to the Bouncy
> Castle implementation, which is SUF-CMA compliant.
> Besides, it appears that the ed22519-java project is not longer maintained,
> as the issue is fixed in the main project of i2p, but not in this separated
> crypto library. As Bouncy Castle is already supported in SSHD and is SUF-CMA
> compliant, it would be very useful that SSHD supports the Bouncy Castle
> implementation of ed25519. This issue is related to SSHD-985 and SSHD-988.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
