l.org" openssl-dev@openssl.orgFrom: "Salz, Rich" <rs...@akamai.com>
Sent by: owner-openssl-...@openssl.orgDate: 06/04/2014 02:31AM
Subject: RE: patch for make depend, chacha
Is there somebody working on it to get Chacha/Poly cipher suites production ready?
It's expected that th
Hi Peter and Rich,
thx for your answer, I needed to decipher them first though ;-)
(http://marc.info/?l=openssl-devm=140181264527042w=2,
http://marc.info/?l=openssl-devm=140186408414195w=2).
1-2 points to this:
If it's broken (@Peter) why is it in the git tree or why was it accepted?
Google's
On Wed, Jun 4, 2014 at 8:35 AM, Dirk Wetter d...@testssl.sh wrote:
If it's broken (@Peter) why is it in the git tree or why was it accepted?
It would be best if that branch were dropped. It's not maintained and
doesn't reflect the current spec.
Cheers
AGL
Hi,
pls see attached.
Is there somebody working on it to get Chacha/Poly cipher suites production
ready?
Cheers,
Dirk
--- crypto/chacha/Makefile.orig 2014-06-03 10:49:51.082287334 +0200
+++ crypto/chacha/Makefile 2014-06-03 10:50:07.496433689 +0200
@@ -21,7 +21,7 @@
APPS=
Is there somebody working on it to get Chacha/Poly cipher suites production
ready?
It's expected that the way the ciphers are used will change as it goes through
the IETF TLS group. Therefore, Google has not been encouraging folks to pick up
and use these patches other than an on your own
