openbsd/src/lib/libssl, branch libressl-v3.6.0 A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=libressl-v3.6.0 2022-09-17T17:14:06+00:00 Allow TLSv1.3 clients to send CCS without middlebox compatibility mode. 2022-09-17T17:14:06+00:00 jsing 2022-09-17T17:14:06+00:00 urn:sha1:74f7c264c9c7cf9fa2bbccfe73e2d98bf2e07476 While RFC 8446 is clear about what legacy session identifiers can be sent by a TLSv1.3 client and how middlebox compatibility mode is requested, it is delightfully vague about the circumstances under which a client is permitted to send CCS messages. While it does not make sense for a client to send CCS messages when they are not requesting middlebox compatibility mode, it is not strictly forbidden by the RFC and at least one (unknown) TLSv1.3 stack has been observed to do this in the wild. Revert part of the previous change and allow clients to send CCS messages, even if they are not requesting middlebox compatibility mode. Found the hard way by florian@ ok tb@ Link to SSL_read_early_data(3) 2022-09-17T16:03:21+00:00 kn 2022-09-17T16:03:21+00:00 urn:sha1:70f7b2faa17684b3944dd57095e0993328b1b4a3 OK tb Enforce the minimum TLS version requirement for QUIC. 2022-09-11T18:13:30+00:00 jsing 2022-09-11T18:13:30+00:00 urn:sha1:f09ab23dacefdbeea6947b43abb45f2e5c0e1f71 ok tb@ Crank major after symbol addition and libcrypto major bump 2022-09-11T17:42:55+00:00 tb 2022-09-11T17:42:55+00:00 urn:sha1:7965f067fc94a2868d0ed31e944bd1291fa37167 Update Symbols.list 2022-09-11T17:42:09+00:00 tb 2022-09-11T17:42:09+00:00 urn:sha1:be5d3d0a6aa7cdc96aa65a048b8df38301ca8972 ok jsing Expose SSL_get_share_{group,curve}() and related #defines 2022-09-11T17:39:46+00:00 tb 2022-09-11T17:39:46+00:00 urn:sha1:0107acd5ff51dd9f40cc92e72939d951c0d39248 ok jsing Expose some error codes needed for QUIC support 2022-09-11T17:38:58+00:00 tb 2022-09-11T17:38:58+00:00 urn:sha1:9923e9738710aa1c844ada328a464bb1c31f714c ok jsing Be stricter with middlebox compatibility mode in the TLSv1.3 server. 2022-09-11T14:39:44+00:00 jsing 2022-09-11T14:39:44+00:00 urn:sha1:18e969fcaab4b90e355dfa70b51b5b8f82050f0b Only allow a TLSv1.3 client to request middlebox compatibility mode if this is permitted. Ensure that the legacy session identifier is either zero length or 32 bytes in length. Additionally, only allow CCS messages on the server side if the client actually requested middlebox compatibility mode. ok tb@ Only permit CCS messages if requesting middlebox compatibility mode. 2022-09-11T14:33:07+00:00 jsing 2022-09-11T14:33:07+00:00 urn:sha1:0ce983d909a52ac43f5a552e4fd367d06492b96f Currently the TLSv1.3 client always permits the server to send CCS messages. Be more strict and only permit this if the client is actually requesitng middlebox compatibility mode. ok tb@ Use CBS when procesing a CCS message in the legacy stack. 2022-09-11T13:51:25+00:00 jsing 2022-09-11T13:51:25+00:00 urn:sha1:9759eb94fea75dec5994ef12ce771d94df4c63b7 ok tb@