On Wednesday 13 January 2016 17:48:37 Salz, Rich wrote:
> We (OpenSSL) have already tested interop of chacha/poly with other
> browsers and TLS stacks, and now it all works. (The official IETF
> version, not the QUIC version).
I was able to confirm interoperability between tlslite-ng[1] and curre
On Mon, Jan 18, 2016 at 12:08:22PM +0100, Kurt Roeckx wrote:
> On Mon, Jan 18, 2016 at 02:04:17PM +0700, Peter Dettman wrote:
> > We (BouncyCastle) have just updated our TLS implementations to
> > draft-ietf-tls-chacha20-poly1305-04 and have confirmed interop with OpenSSL.
>
> As far as I know, Op
On Mon, Jan 18, 2016 at 02:04:17PM +0700, Peter Dettman wrote:
> We (BouncyCastle) have just updated our TLS implementations to
> draft-ietf-tls-chacha20-poly1305-04 and have confirmed interop with OpenSSL.
As far as I know, OpenSSL has an outstanding interop issue with
BoringSSL where OpenSSL wou
We (BouncyCastle) have just updated our TLS implementations to
draft-ietf-tls-chacha20-poly1305-04 and have confirmed interop with OpenSSL.
Regards,
Pete Dettman
On 14/01/2016 12:48 AM, Salz, Rich wrote:
> We (OpenSSL) have already tested interop of chacha/poly with other
> browsers and TLS stack
Chrome is also expecting to ship the cipher in Chrome 49. It's available in
Canary and Dev channel right now. It should interop with OpenSSL's master
branch as of when I last tested this.
David
On Wed, Jan 13, 2016 at 12:48 PM Salz, Rich wrote:
> We (OpenSSL) have already tested interop of chac
We (OpenSSL) have already tested interop of chacha/poly with other browsers and
TLS stacks, and now it all works. (The official IETF version, not the QUIC
version).
We (Akamai) are planning on enabling it for our customers in a few weeks, in
case anyone might be interested.
Thanks.
