Revision 4264ecd4cebf7cee4bd437f1739e9f4297ae5b70 authored by Matt Caswell on 01 May 2020, 08:17:40 UTC, committed by Matt Caswell on 06 May 2020, 10:49:59 UTC
We were not correctly detecting whether TLSv1.3 ciphersuites could actually be supported by the available provider implementations. For example a FIPS client would still offer CHACHA20-POLY1305 based ciphersuites even though it couldn't actually use them. Similarly on the server would try to use CHACHA20-POLY1305 and then fail the handshake. Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org> (Merged from https://github.com/openssl/openssl/pull/11700)
1 parent 15dd075
File | Mode | Size |
---|---|---|
VMSify-conf.pl | -rw-r--r-- | 1.4 KB |
engine.opt | -rw-r--r-- | 152 bytes |
openssl_ivp.com.in | -rw-r--r-- | 1.8 KB |
openssl_shutdown.com.in | -rw-r--r-- | 1.4 KB |
openssl_startup.com.in | -rw-r--r-- | 4.4 KB |
openssl_utils.com.in | -rw-r--r-- | 327 bytes |
test-includes.com | -rw-r--r-- | 752 bytes |
translatesyms.pl | -rw-r--r-- | 1.9 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...