-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chacha20-poly1305 support #64
Comments
It will be a useful addition, true. I'll slowly investigate the options here. OTOH The branch needs a little more polish in some modes to get merged, and is the very next thing on TODO. |
according to the IETF tls working group mailing list, this is not yet standardised (crypto and algorithms are, ciphersuite isn't). a draft (which is not precise) is at https://tools.ietf.org/html/draft-mavrogiannopoulos-chacha-tls-05 and will get more precise and might be published on standard track http://www.ietf.org/mail-archive/web/tls/current/msg16322.html |
Now, this is not to say ChaCha/Poly will not happen, but, uhm, this. |
FWIW I believe this is no longer in
|
ChaCha20-Poly1305 has been adopted as RFC7539, and will be useful when it is approved for TLS.
Although Chrome already uses it, so it might be useful even before that.
It is a lot faster than AES-GCM when there is no hardware acceleration available, especially on ARM, but AFAIK ocaml-nocrypto doesn't use AES-NI so ChaCha20-Poly1305 will probably always be faster.
The text was updated successfully, but these errors were encountered: