tree 2f14b8d051c59444db5a622ca5fa64d8493fe3cf
parent 4cc36adf5a62ff1366e8e9a4d40d9c007c0c8927
author David Benjamin <davidben@chromium.org> 1450562284 -0500
committer Adam Langley <agl@google.com> 1450826252 +0000

Route DHE through the SSL_ECDH abstraction as well.

This unifies the ClientKeyExchange code rather nicely. ServerKeyExchange
is still pretty specialized. For simplicity, I've extended the yaSSL bug
workaround for clients as well as servers rather than route in a
boolean.

Chrome's already banished DHE to a fallback with intention to remove
altogether later, and the spec doesn't say anything useful about
ClientDiffieHellmanPublic encoding, so this is unlikely to cause
problems.

Change-Id: I0355cd1fd0fab5729e8812e4427dd689124f53a2
Reviewed-on: https://boringssl-review.googlesource.com/6784
Reviewed-by: Adam Langley <agl@google.com>