diff options
| author | tb <> | 2022-02-05 18:18:18 +0000 |
|---|---|---|
| committer | tb <> | 2022-02-05 18:18:18 +0000 |
| commit | 853bb6e844ee6365e958fc2e64686a6fdd24459c (patch) | |
| tree | 26b86cb618fa624cd2a6c747425dd6207aa32c42 /src/lib/libc/stdlib/realpath.3 | |
| parent | c7cd75e51d33708442e984b9b2e0ef9c09472ae7 (diff) | |
| download | openbsd-853bb6e844ee6365e958fc2e64686a6fdd24459c.tar.gz openbsd-853bb6e844ee6365e958fc2e64686a6fdd24459c.tar.bz2 openbsd-853bb6e844ee6365e958fc2e64686a6fdd24459c.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/lib/libc/stdlib/realpath.3')
0 files changed, 0 insertions, 0 deletions