[ 
https://issues.apache.org/jira/browse/SSHD-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134985#comment-17134985
 ] 

Matt Sicker commented on SSHD-704:
----------------------------------

I started looking into how this could be implemented, and figuring out an 
appropriate API to use for obtaining the {{u}} value from the X25519 public key 
either requires using 
[XECPublicKeySpec|https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/security/spec/XECPublicKeySpec.html]
 or what I can assume is the [proper API in 
Bouncycastle|https://www.bouncycastle.org/docs/docs1.5on/org/bouncycastle/crypto/params/X25519PublicKeyParameters.html]
 to get the already encoded version of that. I tried using the encoded form of 
the key from the {{KeyPairGenerator}}, but the public key is returned as an 
X.509 key, and converting that to the spec class is a Java 11 API.

> Add support for [email protected]  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
> * [[email protected] kexy exchange 
> specification|https://git.libssh.org/projects/libssh.git/tree/doc/[email protected]]
> * [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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to