True, but there’s currently no flag defined for just “ChaCha20” ciphers, just SSL_CHACHA20POLY1305. My understanding is that CHACHA20POLY1305 is considered AEAD, so the two will always be linked. That being said, nothing prevents CHACHA20 from referencing additional CHACHA20 ciphers, nor precludes adding CHACHA20POLY1305 as a cipher string.
-- -Todd Short // [email protected]<mailto:[email protected]> // "One if by land, two if by sea, three if by the Internet." On Dec 28, 2015, at 10:28 AM, Kurt Roeckx via RT <[email protected]<mailto:[email protected]>> wrote: On Mon, Dec 28, 2015 at 03:01:28PM +0000, Short, Todd via RT wrote: Hello OpenSSL.org<http://OpenSSL.org><http://OpenSSL.org>: This is a patch for the master branch. The changes in master to add ChaCha20 to OpenSSL do not include an alias for the cipher in the "openssl cipher" command, nor in the cipher functions., even though the necessary constants have been defined. The attached patch adds that alias. The following openssl commands now behave as expected: openssl ciphers CHACHA20 openssl ciphers CHACHA20:AES Please at least also update the documentation, like ciphers.pod. I'm also not sure if CHACHA20 should only select those in combination with Poly1305, even if those are currently the only supported. Kurt _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
