[ https://issues.apache.org/jira/browse/SSHD-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220379#comment-17220379 ]
Matt Sicker commented on SSHD-704: ---------------------------------- I've done some testing, and it seems that both the Java 11 version of XDH as well as the BouncyCastle version, while they use incompatible APIs to some extent, they both support encoding and decoding public keys in X.509 format which is almost as simple as the raw public key bytes (in X25519 and X448 public keys encoded into X.509, they're both encoded OID sequences followed by the key data). Since both curves use fixed-size keys, all the DER/ASN.1 logic is also constant. Using the X509EncodedKeySpec class from the JDK allows either to work; they both require a KeyFactory to convert the X509 key into the KeyAgreement key objects needed for the key exchange. > Add support for curve25519-sha...@libssh.org key exchange > ---------------------------------------------------------- > > Key: SSHD-704 > URL: https://issues.apache.org/jira/browse/SSHD-704 > Project: MINA SSHD > Issue Type: Improvement > Affects Versions: 1.4.0 > Reporter: Lyor Goldstein > Priority: Major > Labels: features > Attachments: Curve25519.java, Curve25519SHA256AbstractDH.java, > Curve25519SHA256DHFactory.java, Curve25519SHA256KeyExchange.java, > Curve25519SHA256KeyExchangeFactory.java > > > See > * [curve25519-sha...@libssh.org kexy exchange > specification|https://git.libssh.org/projects/libssh.git/tree/doc/curve25519-sha...@libssh.org.txt] > * [Secure Shell (SSH) Key Exchange Method using Curve25519 and > Curve448|https://tools.ietf.org/html/draft-ietf-curdle-ssh-curves-06] > * [JEP 324: Key Agreement with Curve25519 and > Curve448|http://openjdk.java.net/jeps/324] -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org