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

Jeremy Norris commented on SSHD-1017:
-------------------------------------

I've not researched the Bouncy Castle implementation to determine if it would 
be feasible. For the JSch implementation, I was attempting to avoid adding a 
dependency on an alternate security provider and came across the implementation 
in the OpenJAX project (which appears to be derived from the C version at 
https://github.com/floodyberry/poly1305-donna). I wrote some unit tests for the 
OpenJAX implementation using the RFC 7539 test vectors and some additional 
vectors from the BoringSSL project from Google to confirm that it seemed to 
work correctly.
I would assume that if Bouncy Castle allows instantiating a Poly1305 
javax.crypto.Mac instance (via something like Mac.getInstance("Poly1305")), 
then it would be usable.
I think it would be valuable if the community could propose an RFC 
implementation for SSH that adheres to the RFC 7539 definitions, but I'm not 
sure if it matters unless the OpenSSH project decides to implement it, since 
they are the defacto reference implementation for SSH.

> Add support for chacha20-poly1...@openssh.com
> ---------------------------------------------
>
>                 Key: SSHD-1017
>                 URL: https://issues.apache.org/jira/browse/SSHD-1017
>             Project: MINA SSHD
>          Issue Type: New Feature
>            Reporter: Matt Sicker
>            Priority: Major
>
> See [protocol 
> details|https://github.com/openbsd/src/blob/master/usr.bin/ssh/PROTOCOL.chacha20poly1305].
> * [RFC 7539|https://tools.ietf.org/html/rfc7539] describes the 
> ChaCha20-Poly1305 algorithm.
> * [Dropbear 
> implementation|https://github.com/mkj/dropbear/blob/master/chachapoly.c]
> * [OpenSSH 
> implementation|https://github.com/openbsd/src/blob/master/usr.bin/ssh/cipher-chachapoly-libcrypto.c]
> The cipher is provided by Bouncycastle.
> As a bonus, this could potentially be adapted to propose an equivalent 
> AES/GCM cipher encoding to how OpenSSH implements this ChaCha20-Poly1305 
> cipher.



--
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

Reply via email to