5683 Commits

Author	SHA1	Message	Date
openssl-machine	eb917f4293	Copyright year updates ... Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> Release: yes	2025-04-08 13:07:23 +00:00
Samson S. Kolge	88ecf93695	Fix SSL_new() with QUIC_server_method and improve formatting (Fixes #27255) ... Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27264) (cherry picked from commit 5341e271d9)	2025-04-05 09:15:56 -04:00
Benjamin Kaduk	d48c2cb6ec	statem: always save sigalgs during PHA ... We use the same extension-parsing function on server and client for convenience, but while the server might worry about tracking what was previously received and not overwriting it, on the client receiving a request for post-handshake authentication, we always want to use the values from the current extension (and should always have a new session object that we are free to mutate). It is somewhat unclear whether the server also needs the check for a resumed connection; it appears to have been added back in 2015 in commit 062178678f as part of a broad pass to handle extensions on resumption, but without specific documentation of each extension's handling. Fixes: #10370 Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/24651) (cherry picked from commit ddd99d52d3)	2025-04-01 15:11:47 +02:00
Viktor Dukhovni	a7f3550855	Fix sigalg corner cases ... - Tolerate RSA PKCS#1 *certificate* signatures when the peer sigals include RSA PSS with the same digest. Now that we're more strict about not sending sigalgs that are out of protocol range, when the client supports TLS 1.3 only, we might refuse to return an RSA PKCS#1-signed cert. - Don't send TLS 1.3 sigalgs when requesting client certs from a TLS 1.2 client. Fixes: #1144 Fixes: #25277 Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27166) (cherry picked from commit a5f98e6da5)	2025-03-31 14:08:12 +02:00
Viktor Dukhovni	c2f50863b5	Fix goto label indents to match style ... Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Paul Dale <ppzgs1@gmail.com> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27175) (cherry picked from commit 60f2a71400)	2025-03-28 11:37:31 +01:00
jay9827342	070856e952	Memory leak fix ktls_meth.c ... The OSSL_RECORD_LAYER needs to be properly freed when return code isnt success. Memory leak fix CLA: trivial Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Paul Yang <kaishen.yy@antfin.com> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27111) (cherry picked from commit e5e4cf41c7)	2025-03-25 20:22:51 +01:00
openssl-machine	b17e3bb6ce	Copyright year updates ... Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> Release: yes	2025-03-25 14:59:38 +00:00
Bernd Edlinger	1e6bd53cfc	Try to fix reported qlog issues ... Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27089) (cherry picked from commit 9f85a036e3)	2025-03-24 20:21:42 +01:00
Tomas Mraz	56e00f1296	qlog_event_helpers.c: Fix inverted condition ... We want to skip up to PACKET_remaining() and not "at least" PACKET_remaining() bytes. Reviewed-by: Paul Dale <ppzgs1@gmail.com> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27138) (cherry picked from commit 83b11af017)	2025-03-24 15:23:09 +01:00
Matt Caswell	fb55383c65	Move the Handshake read secret change earlier in the process for QUIC 0-RTT ... On the server side we were changing the handshake rx secret a little late. This meant the application was forced to call SSL_do_handshake() again even if there was nothing to read in order to get the secret. We move it a little earlier int the process to avoid this. Fixes the issue described in: https://github.com/ngtcp2/ngtcp2/pull/1582#issuecomment-2735950083 Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27101) (cherry picked from commit 95051052b3)	2025-03-20 20:22:53 +01:00
Matt Caswell	6e4ddabd98	Fix the use of CCM ciphersuites with QUIC TLS API ... Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27091) (cherry picked from commit 207cd5bb97)	2025-03-20 11:25:01 +01:00
Matt Caswell	688cea710d	Always use NULL BIOs when using the QUIC TLS API ... Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27091) (cherry picked from commit 228a26fde4)	2025-03-20 11:24:59 +01:00
Matt Caswell	d8ce455a3d	Ensure SSL_get_app_data() continues to work even in SSL_free() ... During SSL_free() we may get a QUIC TLS callback being called to clean up any remaining record data. We should ensure that SSL_get_app_data() continues to work, even in this scenario. Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27091) (cherry picked from commit 2100cf2ee0)	2025-03-20 11:24:57 +01:00
Matt Caswell	81789a05b7	Don't decrement the unreleased counter if we failed to release a record ... In a failure situation we may incorrectly decrement the amount of data released. Only decrement the counter if we successfully released. Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27091) (cherry picked from commit 4ad45969b0)	2025-03-20 11:24:57 +01:00
openssl-machine	0c679f5566	Copyright year updates ... Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> Release: yes	2025-03-12 13:35:59 +00:00
Viktor Dukhovni	91c6e157c6	Make group names case-insensitive ... Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Paul Dale <ppzgs1@gmail.com> Reviewed-by: Saša Nedvědický <sashan@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26991)	2025-03-09 23:31:25 +01:00
Viktor Dukhovni	bcff020c36	Refactor sigalg handling ... - The default sigalg list now puts ML-DSA-65 first, then ML-DSA-87 and then ML-DSA-44. (87 vs. 44 Subject to bikeshedding). - The mintls and maxtls versions are now taken into account for both built-in and provided algorithms. - Some algorithms have a separate TLSv1.2-specific name for future reporting via openssl-list(1). - ML-DSA aside, any new provided algorithms go at the end of the default list (backwards-compatible inclusion). - The built-in algorithms now also have min/max DTLS versions. Though the provider TLS-SIGALG capability was extended to also report the DTLS version range, the minimum supported DTLS is 1.3, which we don't yet have, so it is not yet possible to add DTLS sigalgs via a provider - The TLS 1.3 brainpool sigalgs got their correct IANA names, with the legacy names as purported TLS 1.2 alternatives, but since these are for TLS 1.3 and up those names are for matching only, the reported value will still be the 1.3 name. Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26975)	2025-03-09 23:19:37 +01:00
Neil Horman	9a308a89a4	Orphan packets from qrx ... It may occur that the qrx we allocate in port_default_packet handler to do AEAD validation isn't the one the channel ultimately uses (like if we turn off address validation). In that event, we need to ensure that anything we have on that qrx isn't returned to its free list to avoid early freeing when we free the qrx at the end of port_default_packet_handler, while those frames are still pending on the channel qrx Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27004)	2025-03-09 18:44:53 +01:00
Neil Horman	8f74d8cee3	If our server channel creates its own qrx, set its initial secret ... With the addition of larger client hellos, stemming from the use of larger PQC key shares, it may happen that we get a client hello accross multiple datagrams. Normally this is not a problem as port_default_packet_handler allocates a qrx and initializes its initial secret immediately. But if server address validation is disabled, then the channel creates the qrx in port_bind_channel itself, without initial secrets. As a result, we validate the first datagram in port_default_packet_handler, but the subsequent datagrams containing the remaining client hello fragments fail decode. Fix it by ensuring that we add the initial secret in port_bind_channel if we don't give it a preconfigured qrx Fixes openssl/project#1131 Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Viktor Dukhovni <viktor@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27006)	2025-03-07 21:56:34 -05:00
Neil Horman	c0251d7b0f	Fix build on windows xp ... Windows XP doesn't support setting socket handles to be non-inheritable, but the rio_notifier attempts to do so. WSASocketA will there return an error when the NO_INHERIT flag is set. In that case, just retry the call without the flag. Fixes #26943 Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26970)	2025-03-05 17:36:20 +01:00
daum3ns	30fbc68dd4	tls_validate_record_header(): Check for all HTTP methods ... The change checks for all HTTP methods in ssl_record, not only GET, POST, PUT and HEAD. (additionally PATCH, DELETE, OPTIONS and TRACE) CLA: trivial Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26968)	2025-03-05 14:58:29 +01:00
Matt Caswell	5eb55ad8a7	Fix a compilation failure in AIX ... AIX (at least for 7.1) defines some macros for "events" and "revents" which interferes with our own use of these names. Fixes #24236 Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26933)	2025-03-04 09:02:15 -05:00
Matt Caswell	aaad33c5ac	Move ssl_err.c into libcrypto ... We move ssl_err.c out of libssl and into libcrypto. This file is entirely self contained and is used to load error strings into the libcrypto error tables. By moving this file into libcrypto, libssl can be unloaded safely without having dangling references to this error information. Fixes #26672 Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26931)	2025-03-01 14:46:03 -05:00
Andrew Dinh	442f1958e8	QUIC NULL checks ... - Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643029 - Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643030 - Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643141 Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26916)	2025-02-27 10:23:38 -05:00
Neil Horman	2ce46ad8ce	Change cipher suite alert for 0 length cipher_suites ... From RFC 8446: Note: TLS defines two generic alerts (see Section 6) to use upon failure to parse a message. Peers which receive a message which cannot be parsed according to the syntax (e.g., have a length extending beyond the message boundary or contain an out-of-range length) MUST terminate the connection with a "decode_error" alert. Peers which receive a message which is syntactically correct but semantically invalid (e.g., a DHE share of p - 1, or an invalid enum) MUST terminate the connection with an "illegal_parameter" alert. A zero length cipher suite list I think is considered out of range, and so we should return "decode_error" rather than "illegal_parameter" Fixes #25309 Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26781)	2025-02-25 15:31:45 -05:00
Alexandr Nedvedicky	395a83a617	Fix read out of buffer bounds when dealing with BIO_ADDR ... This issue was discoevered while I was testing SSL_new_from_listener() using a newly created unit test. It has turned out the QUIC stack at few places contain pattern as follows: foo(QUIC_WHATEVER *q, BIO_ADDR *a) { q->a = *a; } The problem is that derefencning a that way is risky. If the address `a` comes from BIO_lookup_ex() it may actually be shorter than sizeof(BIO_ADDR). Using BIO_ADDR_copy() is the right thing to do here. Fixes #26241 Reviewed-by: Viktor Dukhovni <viktor@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26252)	2025-02-25 15:55:46 +01:00
Tomas Mraz	be5965acad	add_uris_recursive(): Avoid OSSL_STORE_INFO leak on error ... Fixes #26480 Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Viktor Dukhovni <viktor@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26511)	2025-02-25 15:50:45 +01:00
Tomas Mraz	87b5aa737d	Rename fnv1a_hash() to ossl_fnv1a_hash() ... It is no longer static. Also add it to libssl only with quic enabled. Reviewed-by: Paul Dale <ppzgs1@gmail.com> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26882)	2025-02-25 15:45:42 +01:00
Tomas Mraz	4c69caef48	tls1_set_groups_list(): Update raised errors ... Do not raise ERR_LIB_CONF codes from libssl. Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26801)	2025-02-25 15:34:24 +01:00
Tomas Mraz	0b40fac3fb	tls_construct_ctos_key_share(): Fix handling of HRR without key share request ... Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26801)	2025-02-25 15:34:24 +01:00
Tomas Mraz	a3143c2400	No valid groups is not an error ... Of course TLS-1.3 won't be usable with such configuration. Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26801)	2025-02-25 15:34:24 +01:00
Tomas Mraz	a89c99e04b	Have the same default groups list for QUIC and TLS ... Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26801)	2025-02-25 15:34:23 +01:00
Viktor Dukhovni	63a70d63e2	Add hybrid ML-KEM based groups to default TLS groups ... - send two key shares by default - trim down the list of default groups The default TLS group list setting is now: ?*X25519MLKEM768 / ?*X25519:?secp256r1 / ?X448:?secp384r1:?secp521r1 / ?ffdhe2048:?ffdhe3072 Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26801)	2025-02-25 15:34:23 +01:00
Alexandr Nedvedicky	96075a6a40	Fix AEAD validation of initial packets in port ... The interoperability tests disable client ip address validation done by RETRY packet. All tests done in CI take code path which sends a retry packet. The first initial packet sent by client uses a different initial encryption level keys to protect packet integrity. The keys are derived from DCID chosen by client. When server accepts connection on behalf of initial packet, the 'DCID' gets changed which means the initial level encryption keys are changing too. So when server skips sending a retry packet, it must forget the qrx which was used to validate initial packet sent by client. Forgetting qrx is not straightforward, we must salvage the unencrypted packets left there after they were validated. Those unencrypted packets must be injected to newly created channel. Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26808)	2025-02-25 12:05:10 +01:00
Alexandr Nedvedicky	c14ae04613	Perform initial AEAD validation before creating a channel ... We let port to create qrx object and use it for packet validation. If packet validates, we then create channel and pass pre-created qrx to channel's constructor. Co-authored-by: Andrew Dinh <andrewd@openssl.org> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26808)	2025-02-25 12:04:09 +01:00
Andrew Dinh	cec0659fa4	Coverity fixes ... Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643042 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643047 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643089 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643091 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643095 Reviewed-by: Paul Dale <ppzgs1@gmail.com> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26845)	2025-02-25 08:55:26 +01:00
Neil Horman	1eb5ffcdc8	Fix ci break on building quic with no-siphash ... SHARED_SOURCE doesn't pull in siphash if its disabled in the configuration leading to undefined symbols, which we need for quic. If siphash is disabled in the build, then pull it in via a SOURCE addition, otherwise pull it in via SHARED_SOURCE Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26874)	2025-02-23 17:16:03 -05:00
Neil Horman	17d2fd0752	Use siphash to implement lcidm hash function ... Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26849)	2025-02-22 13:23:16 -05:00
Neil Horman	7dd821bab5	Add siphash to shared source for quic ... Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26849)	2025-02-22 13:23:16 -05:00
Neil Horman	6a9a9480a7	Update LCIDM lookups to include hash keys ... In preparation for using siphash in our hash function Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26849)	2025-02-22 13:23:16 -05:00
Neil Horman	3e3942b42f	Add random hash key value to lcidm struct ... This is in preparation for using siphash to compute lcidm hash table values Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26849)	2025-02-22 13:23:16 -05:00
Andrew Dinh	704c3d3cd2	Various NULL checks ... Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643035 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643039 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643041 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643044 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643045 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643046 Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26840)	2025-02-21 15:07:27 -05:00
Cheng Zhang	db2c54cc92	Added new API to enable 0-RTT for 3rd party QUIC stacks. ... Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26842)	2025-02-21 12:01:30 +01:00
Andrew Dinh	a1c6e2d1b5	ssl_lib.c: Check for NULL from SSL_CONNECTION_FROM_SSL() ... Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643027 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643028 Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26824)	2025-02-20 15:30:25 +01:00
Andrew Dinh	3820f2da7c	NULL checks for QUIC code ... Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643033 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643032 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643031 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643030 Fixes https://scan5.scan.coverity.com/#/project-view/62507/10222?selectedIssue=1643029 Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26825)	2025-02-20 08:13:02 -05:00
Cheng Zhang	1b3f27f920	Add the SSL_NO_EOED internal macro ... The TLS EndOfEarlyData message is not applicable in some scenarios (e.g., QUIC). This adds a macro to handle this message. Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26552)	2025-02-19 17:27:04 +01:00
Viktor Dukhovni	76e3fdd0f6	ssl3_ctrl(): Fix condition in SSL_CTRL_GET_PEER_SIGNATURE_NAME ... Reviewed-by: Kurt Roeckx <kurt@roeckx.be> Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Paul Dale <ppzgs1@gmail.com> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26819)	2025-02-19 17:23:04 +01:00
Neil Horman	84694d2baa	Relax checking of supported-groups/keyshare ordering ... quic interop testing showed that interop with the mvfst client was failing, due to detecting mis ordering of supported groups and keyshare extensions This is strictly a mvfst problem to fix, but RFC 8446 indicates that we MAY check the ordering but don't strictly have to. We've opened an issue with the client to fix this, but in the interests of client compatibility relax the ordering check so that, instead of issuing a fatal alert, we just log a trace message indicating the discrepancy Fixes openssl/project#1106 Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Viktor Dukhovni <viktor@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26818)	2025-02-19 17:08:53 +01:00
Frederik Wedel-Heinen	00fbc96988	Adds missing checks of return from XXX_up_ref(). ... Reviewed-by: Saša Nedvědický <sashan@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26294)	2025-02-18 16:32:59 +01:00
Viktor Dukhovni	d5a4665a21	Case-insensitive sigalgs ... Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> (Merged from https://github.com/openssl/openssl/pull/26767)	2025-02-18 14:24:57 +11:00