diff options
author | tb <> | 2022-02-05 18:18:18 +0000 |
---|---|---|
committer | tb <> | 2022-02-05 18:18:18 +0000 |
commit | e5500000382c402276da7446a43a82d0153d2f1d (patch) | |
tree | 26b86cb618fa624cd2a6c747425dd6207aa32c42 /src/regress/lib/libssl/unit/ssl_get_shared_ciphers.c | |
parent | 47e61a82f45737b7e9b4494d8a64d4a2f108e9de (diff) | |
download | openbsd-e5500000382c402276da7446a43a82d0153d2f1d.tar.gz openbsd-e5500000382c402276da7446a43a82d0153d2f1d.tar.bz2 openbsd-e5500000382c402276da7446a43a82d0153d2f1d.zip |
Switch TLSv1.3 cipher names from AEAD- to OpenSSL's TLS_
OpenSSL chose to break the previous naming convention for ciphers and
to adopt TLS_* "RFC" names instead. Unfortunately, these names are
exposed in several APIs and some language bindings test for these
non-standard names instead of cipher values, which is ... unfortunate
(others would say "plain crazy").
We currently have to maintain patches in regress and ports (p5-Net-SSLeay,
openssl-ruby-tests - which means that Ruby will pick this up at some point)
to work around this difference and that's just not worth the effort.
The old AEAD- names will become aliases and continue to work, but in
openssl ciphers and netcat output the TLS_* names will now be displayed.
"I would be very happy if this gets committed" bluhm
ok beck inoguchi, begrudgingly ok jsing
Diffstat (limited to 'src/regress/lib/libssl/unit/ssl_get_shared_ciphers.c')
0 files changed, 0 insertions, 0 deletions