diff options
author | Fred Hebert <[email protected]> | 2016-10-20 13:55:45 -0400 |
---|---|---|
committer | Fred Hebert <[email protected]> | 2016-11-02 10:47:28 -0400 |
commit | bd0f19c6fa1944365edf03febf75354642fc2240 (patch) | |
tree | f0c86f6f0ce5602b859c63b41999d7e0a4eb2eb4 /lib/ssl/test/ssl_alpn_handshake_SUITE.erl | |
parent | 9a7f521f9d6eba398af2e703863f9975911085a4 (diff) | |
download | otp-bd0f19c6fa1944365edf03febf75354642fc2240.tar.gz otp-bd0f19c6fa1944365edf03febf75354642fc2240.tar.bz2 otp-bd0f19c6fa1944365edf03febf75354642fc2240.zip |
Add ECC curve selection order config in TLS server
As per RFC 4492 Sec 5.1, the preferred order of selection of named
curves is based on client preferences.
Currently, the SSL application only picks entries according to the
absolute order of entries as tracked in a hardcoded list in code.
This patch changes things so that the client-specified order is
preferred. It also allows a mode where the server can be configured to
override the client's preferred order with its own, although the chosen
ECC must still be within both lists.
The configuration is done through the following options:
- `eccs`, shared by clients and servers alike, allows the specification
of the supported named curves, in their preferred order, and may
eventually support more values for explicit primes and so on.
- `honor_ecc_order`, a server-only option, is similar to
`honor_cipher_order` and will, by default let the server pick the
client-preferred ECC, and otherwise pick the server-preferred one.
The default value for `eccs` is the same as before, although the
server-chosen ECC now defaults to the client rather than previous
choice.
A function `ssl:eccs()` has been added that returns the highest
supported ECCs for the library.
Diffstat (limited to 'lib/ssl/test/ssl_alpn_handshake_SUITE.erl')
0 files changed, 0 insertions, 0 deletions