summaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* Copyright year updatesopenssl-machine2026-04-0710-10/+10
| | | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Eugene Syromiatnikov <[email protected]> MergeDate: Tue Apr 7 12:24:30 2026 Release: yes
* Apply clang-format to the source treeEugene Syromiatnikov2026-04-034-70/+56
| | | | | | | | | | | | | | Ensure that all the source files are formatted with the current .clang-format configuration, to avoid spurious clang-format checker errors when arbitrary files are touched. Signed-off-by: Eugene Syromiatnikov <[email protected]> Reviewed-by: Nikola Pajkovsky <[email protected]> Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> MergeDate: Fri Apr 3 14:49:00 2026 (Merged from https://github.com/openssl/openssl/pull/29822)
* cmp_vfy.c,doc/,test/: when trying to use cached CMP message sender cert, no ↵Dr. David von Oheimb2026-03-251-0/+2
| | | | | | | | | | more check its revocation and chain Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Paul Dale <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28973) (cherry picked from commit 525a4f1efbab0d3c2aff59ab8e671b8d9f35ddee)
* include/openssl/macros.h: add missing #undef OPENSSL_NO_DEPRECATED_3_5Eugene Syromiatnikov2026-03-171-0/+1
| | | | | | | | | | | | | Complements: 0bba82188186 "Deprecate all BIO_meth_get_*() functions" Signed-off-by: Eugene Syromiatnikov <[email protected]> Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Frederik Wedel-Heinen <[email protected]> Reviewed-by: Neil Horman <[email protected]> MergeDate: Tue Mar 17 17:12:18 2026 (Merged from https://github.com/openssl/openssl/pull/30400) (cherry picked from commit 40f076965f154e307a0821088b6adcc447ceae01)
* OSSL_HTTP_REQ_CTX_nbio(): check for clear Content-Type mismatchTom Gautot2026-03-052-2/+3
| | | | | | | | | | | | Fixes #29748 Reviewed-by: David von Oheimb <[email protected]> Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> MergeDate: Thu Mar 5 18:04:24 2026 (Merged from https://github.com/openssl/openssl/pull/29829) (cherry picked from commit 465fd32d3374a7197107ebd9ad09f8844a7d496d)
* Move typedef 'RSA_OEAP_PARAMS' to openssl/types.hgiorgiopapini2026-02-182-2/+4
| | | | | | | | | | | | | | | This avoids redefinition of the type. CLA: trivial Reviewed-by: Shane Lontis <[email protected]> Reviewed-by: Frederik Wedel-Heinen <[email protected]> Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> MergeDate: Wed Feb 18 13:09:26 2026 (Merged from https://github.com/openssl/openssl/pull/29994) (cherry picked from commit 5869303daaecf037f0d00dc33a00f9bdc1e71f2f)
* don't use asm accelerated path on big endian power9Neil Horman2026-02-171-0/+2
| | | | | | | | | | | | | | | | | | | | | | | https://github.com/openssl/openssl/issues/29845 Found that our hardware accelerated path doesn't work on big endian systems, so make sure that we only use it when little endian is defined We also noted that PPC_AES_GCM_CAPABLE gets defined to zero when the capabilities register notes that the hardware isn't capable of the needed instructions, but that still includes the asm path as PPC_AES_GCM_CAPABLE is still defined. Fix both issues Fixes #29845 Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Tom Cosgrove <[email protected]> MergeDate: Tue Feb 17 14:11:46 2026 (Merged from https://github.com/openssl/openssl/pull/29968) (cherry picked from commit b02b04fbad809c82efbf1e3274e6a22caf997b8d)
* Fix coding style check by adding clang format exclusionsrainerjung2026-01-291-0/+6
| | | | | | | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Paul Dale <[email protected]> MergeDate: Thu Jan 29 14:22:55 2026 (Merged from https://github.com/openssl/openssl/pull/29817) (cherry picked from commit bb1f540d0fe00c8293f3983580d6f68bfda3d81e)
* Sparc asm: remove whitespace that breaks asm syntax in generated filesrainerjung2026-01-291-3/+3
| | | | | | | | | | | | | This fixes #29808. Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Paul Dale <[email protected]> MergeDate: Thu Jan 29 14:22:50 2026 (Merged from https://github.com/openssl/openssl/pull/29817) (cherry picked from commit 44699dcc691ee266d22df1795625599a8e112504)
* Fix legitimate spelling errorsRichard Levitte2025-12-211-1/+1
| | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/29461)
* 3.5-POST-CLANG-FORMAT-WEBKIT3.5-POST-CLANG-FORMAT-WEBKITBob Beck2025-12-09334-23608/+23193
| | | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Saša Nedvědický <[email protected]> Reviewed-by: Nikola Pajkovsky <[email protected]> (Merged from https://github.com/openssl/openssl/pull/29262)
* 3.5-PRE-CLANG-FORMAT-WEBKIT3.5-PRE-CLANG-FORMAT-WEBKITBob Beck2025-12-0931-0/+266
| | | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Saša Nedvědický <[email protected]> Reviewed-by: Nikola Pajkovsky <[email protected]> (Merged from https://github.com/openssl/openssl/pull/29262)
* Disable clang format around multi-line macros of sparc assemblyBob Beck2025-12-041-0/+4
| | | | | | | | | | They are not asm, but spit out stuff that is not C Clang-format gets confused and does bad things with them. Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/29261)
* Add SSL_CTX_is_quic APINeil Horman2025-11-251-0/+7
| | | | | | | | | | | | | | | Like SSL_is_quic, it would be helpful to know if SSL_CTX objects create QUIC SSL's or not. Note, this is a public function in the master branch, but is made private for older stable branches, so as not to introduce new public API's there (3.6-3.0) Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Matt Caswell <[email protected]> (Merged from https://github.com/openssl/openssl/pull/29193) (cherry picked from commit d010a5b934bf57a7933341ea3bc42aa902996c4b)
* Modernize header macros for C23 compatibilityIgor Ustinov2025-11-043-13/+13
| | | | | | | | | | | | | | | Replace old-style (int (*)()) and (char *(*)()) casts with proper typed prototypes (i2d_of_void *, d2i_of_void *, void *(*)(void)) to comply with stricter C23 function pointer rules. Fixes #27938 Reviewed-by: Richard Levitte <[email protected]> Reviewed-by: Dmitry Belyavskiy <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/29048) (cherry picked from commit 0b7afd6d303d150c13c04f66e77fcbcdaeec2a84)
* Fix memory leak in x509_pubkey_ex_d2i_ex()Andrey Tsygunka2025-10-231-0/+5
| | | | | | | | | | | | | | | | | | | | | | If the call to ASN1_item_ex_d2i() from x509_pubkey_ex_d2i_ex() fails *pval is freed by asn1_item_ex_d2i_intern()->ASN1_item_ex_free()->ossl_asn1_item_embed_free() inside the ASN1_item_ex_d2i() function without freeing the string buffer X509_PUBKEY::propq that was previously allocated in x509_pubkey_ex_new_ex() and we lose the pointer to this buffer. The function we are fixing here is one of the functions used to define X509_PUBKEY - so any operations that work directly on X509_PUBKEY_INTERNAL should be prevented from freeing the structure because they don't know how to handle it. Signed-off-by: Andrey Tsygunka <[email protected]> Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Dmitry Belyavskiy <[email protected]> Reviewed-by: Neil Horman <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27333) (cherry picked from commit 11e1ea9d4d0c9a5e84b944535332aebf673e82f0)
* freebsd ktls: avoid unaligned 16 bit length store in ktls_read_recordJoshua Rogers2025-10-171-1/+2
| | | | | | | | | | | | | This prevents SIGBUS on strict alignment architectures when p+3 is not aligned for 16 bit access. Behavior is unchanged on x86 and matches the Linux path. Signed-off-by: Joshua Rogers <[email protected]> Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28860) (cherry picked from commit c33120d0e403b4079e5104fd20040a51930e8d8e)
* CMS: Produce error when AEAD algorithms are used in enveloped dataJakub Zelenka2025-10-171-0/+1
| | | | | | | | | | Fixes GH-21414 Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27772) (cherry picked from commit 2dda0c50eafc1de8a2c008fbf60340ba5e60bfb3)
* ktls: move ktls_enable() within ktls_start()Ulrich Weber2025-10-141-0/+6
| | | | | | | | | | | | | | | | | | | | | On linux ktls can only be enabled on established TCP sockets. When SSL_set_fd() is called before the connection is established ktls_enable() fails and ktls is not setup. This moves ktls_enable() call within then ktls_start() function. Multiple calls to ktls_start() will trigger additional ktls_enable() calls which fail with EEXIST, but do not affect the ktls socket. CLA: trivial Signed-off-by: Ulrich Weber <[email protected]> Reviewed-by: Paul Yang <[email protected]> Reviewed-by: Saša Nedvědický <[email protected]> Reviewed-by: Matt Caswell <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27908) (cherry picked from commit f23f706a26f2e7cd5dd5221d57e2d0db28530f4e)
* Fix OPENSSL_VERSION_NUMBER to always have zero status bitsRichard Levitte2025-09-201-2/+2
| | | | | | | | | | | | | | | | | | The documentation suggested that they were always zero, while the implementation in <openssl/opensslv.h> suggested that it could be 0xf in OpenSSL releases... which (almost) never happened because of a bug in said implementation. Therefore, we solidify that the status bits are indeed always zero, at least in all OpenSSL 3 versions. Resolves: https://github.com/openssl/project/issues/1621 Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28603) (cherry picked from commit 60c4feacce6faf0e98167dc2ab2a1c2e85882049)
* Revert "rsa: expose pairwise consistency test API"Eugene Syromiatnikov2025-09-181-4/+0
| | | | | | | | | | | | | | | | This reverts commit dc5cd6f70a0e "rsa: expose pairwise consistency test API", that has introduced ossl_rsa_key_pairwise_test() function, as the only user has been removed in 7f7f75816f26 "import pct: remove import PCTs for most algorithms". Complements: 7f7f75816f26 "import pct: remove import PCTs for most algorithms" Signed-off-by: Eugene Syromiatnikov <[email protected]> Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Richard Levitte <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28557) (cherry picked from commit 5a299cb0d4c4fa0d7ac25855ceba288278efda7f)
* Copyright year updatesopenssl-machine2025-09-162-2/+2
| | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Matt Caswell <[email protected]> Release: yes
* Add OSSL_SELF_TEST_TYPE_PCT_IMPORT transient error statePauli2025-08-301-0/+1
| | | | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28376) (cherry picked from commit 1dc1de78617a3ef817d845329ad9c7b8c96362a2)
* add new errorPauli2025-08-301-0/+1
| | | | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28376) (cherry picked from commit 9013cca925836ff092cf31acd6edadbbee0c6858)
* slh-dsa: add a PCT for key import when in FIPS modePauli2025-08-291-0/+2
| | | | | | | | | | | | Fixes #28182 Co-Authored-By: slontis <[email protected]> Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28276) (cherry picked from commit 79037022801d6496bb8e1a8a29c21236084c8588)
* Correct the synthetisized OPENSSL_VERSION_NUMBERRichard Levitte2025-08-131-6/+1
| | | | | | | | | | | | | The last hex digit always became 0x0L, even of OPENSSL_VERSION_PRE_RELEASE was the empty string. Resolves: https://github.com/openssl/openssl/issues/28227 Reviewed-by: Paul Yang <[email protected]> Reviewed-by: Paul Dale <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28230) (cherry picked from commit ba2c314a60d9f42d1d2e63ea0f791cc04e03005b)
* Remove OSSL_CRYPTO_ALLOC attribute from CRYPTO_*dup routinesEugene Syromiatnikov2025-08-121-3/+3
| | | | | | | | | | | | | | | | | The __attribute__((malloc)) is for functions that return new memory, and "the memory [returned by the function] has undefined content", which is a property that doesn't hold for the *dup functions (the same reason it doesn't apply to realloc). Fixes: e1035957eba1 "OSSL_CRYPTO_ALLOC attribute introduction proposal." Signed-off-by: Eugene Syromiatnikov <[email protected]> Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Paul Dale <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28220) (cherry picked from commit 85bba74789f82daca7482a9274c6d02843fb2dbb)
* Ensure that the largest_pn values are migrated to our channel qrxNeil Horman2025-08-071-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Recently, our overnight QUIC interop runs began failing in CI when an openssl server was tested against an ngtcp2 client: https://github.com/openssl/openssl/actions/runs/16739736813 The underlying cause bears some explination for historical purposes The problem began happening with a recent update to ngtcp2 in which ngtcp2 updated its wolfssl tls backend to support ML-KEM, which caused ngtcp to emit a client hello message that offered several groups (including X25519MLKEM768) but only provided a keyshare for x25519. This in turn triggered the openssl server to respond with a hello retry request (HRR), requesting an ML-KEM keyshare instead, which ngtcp2 obliged. However all subsequent frames from the client were discarded by the server, due to failing packet body decryption. The problem was tracked down to a mismatch in the initial vectors used by the client and server, leading to an AEAD tag mismatch. Packet protection keys generate their IV's in QUIC by xoring the packet number of the received frame with the base IV as derived via HKDF in the tls layer. The underlying problem was that openssl hit a very odd corner case with how we compute the packet number of the received frame. To save space, QUIC encodes packet numbers using a variable length integer, and only sends the changed bits in the packet number. This requires that the receiver (openssl) store the largest received pn of the connection, which we nominally do. However, in default_port_packet_handler (where QUIC frames are processed prior to having an established channel allocated) we use a temporary qrx to validate the packet protection of those frames. This temporary qrx may be incorporated into the channel in some cases, but is not in the case of a valid frame that generates an HRR at the TLS layer. In this case, the channel allocates its own qrx independently. When this occurs, the largest_pn value of the temporary qrx is lost, and subsequent frames are unable to be received, as the newly allocated qrx belives that the larges_pn for a given pn_space is 0, rather than the value received in the initial frame (which was a complete 32 bit value, rather than just the changed lower 8 bits). As a result the IV construction produced the wrong value, and the decrypt failed on those subsequent frames. Up to this point, that wasn't even a problem, as most quic implementations start their packet numbering at 0, so the next packet could still have its packet number computed properly. The combination of ngtcp using large random values for initial packet numbers, along with the HRR triggering a separate qrx creation on a channel led to the discovery of this discrepancy. The fix seems pretty straightforward. When we detect in port_default_packet_handler, that we have a separate qrx in the new channel, we migrate processed packets from the temporary qrx to the canonical channel qrx. In addition to doing that, we also need to migrate the largest_pn array from the temporary qrx to the channel_qrx so that subsequent frame reception is guaranteed to compute the received frame packet number properly, and as such, compute the proper IV for packet protection decryption. Fixes openssl/project#1296 Reviewed-by: Saša Nedvědický <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28189)
* Copyright year updatesopenssl-machine2025-08-053-3/+3
| | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Matt Caswell <[email protected]> Release: yes
* dh: add FIPS 140-3 PCT on key import.Pauli2025-07-311-1/+1
| | | | | | | | | | This is mandated by FIPS 140-3 IG 10.3.A additional comment 1 Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28122) (cherry picked from commit db969c3ab08240cf9652cb621fbf1936d056464c)
* fips: add DH PCT namePauli2025-07-311-0/+1
| | | | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28122) (cherry picked from commit 88a13095667228c2361361c97704ea992d837ade)
* rsa: expose pairwise consistency test APIPauli2025-07-311-0/+4
| | | | | | | | | | | This is only used by the FIPS provider as part of importing keys. At least at the moment. Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28122) (cherry picked from commit dc5cd6f70a0eeb30e272fe885a64f3e3d76b5e42)
* Make ERR_count_to_mark() available to providers via 'in' dispatch arrayIngo Franzki2025-07-301-0/+4
| | | | | | | | | | | | | | | | | | Functions like ERR_set_mark(), ERR_clear_last_mark(), and ERR_pop_to_mark() are already passed to the a provider via the 'in' dispatch array of the provider initialization function (although the documentation did not mention them). Also pass ERR_count_to_mark() to the provider the same way, and update the documentation to mention all four functions. Signed-off-by: Ingo Franzki <[email protected]> Reviewed-by: Dmitry Belyavskiy <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28073) (cherry picked from commit f77fafd16e92699544466556d368ed7722f49dd8)
* - changes suggested by @t8mAlexandr Nedvedicky2025-07-271-1/+1
| | | | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28023) (cherry picked from commit 92330c8f80e4dbfc45b7718d9ed526f196daba0a)
* ACK manager must avoid infinite probe time when waiting handshake confirmationsashan2025-07-271-1/+1
| | | | | | | | | | | | | | According to RFC 9002, section 6.2.2.1 the client the client must keep PTO (probe time out) armed if it has not seen HANDSHAKE_DONE quic message from server. Not following RFC spec here may cause the QUIC session to stale during TLS handshake. Fixes openssl/project#1266 Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/28023) (cherry picked from commit cdbfacead0d07ed47fa1087d633acf6f6399aa2c)
* fix SM2 privatekey decode(PEM format, ECPrivateKey).Alen Yan2025-07-251-0/+1
| | | | | | | | Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27963) (cherry picked from commit bd172dd0e1b76116402534aa4bb5c89d039e7762)
* Copyright year updatesopenssl-machine2025-07-013-3/+3
| | | | | | Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Neil Horman <[email protected]> Release: yes
* Nit: macro parameters should always be parenthesised in expressionsRichard Levitte2025-06-221-2/+2
| | | | | | | | | | | Affected macros: ossl_likely and ossl_unlikely Reviewed-by: Tim Hudson <[email protected]> Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Neil Horman <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27862) (cherry picked from commit cdd01b5e0734b0324251b32a8edd97f42ba90429)
* Remove _strlen31Neil Horman2025-06-061-11/+0
| | | | | | | | | | | | | | | | | | | | This function is old and fairly broken. Code archeology in our git tree hasn't revealed why it was creted (though it may have possibly been to support older win32 systems that couldn't do 64 bit integers properly, like windows 95/98). There seems to be no good reason to keep it around, and given that it has potentially serious side effects, lets just remove it. Fixes #27761 Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Richard Levitte <[email protected]> Reviewed-by: Tom Cosgrove <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27763) (cherry picked from commit b0d363a2cb039eac2908b7cb00b395235373193e)
* Reset qtls->local_transport_params_consumed to 0 on SSL_clear()Andrew Dinh2025-06-031-0/+2
| | | | | | | | Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27656) (cherry picked from commit 9bad2b86e892b70ea65e87c409ae90f625d3c12c)
* Use value barrier for constant_time_cond_swap_*Jai S2025-06-031-3/+15
| | | | | | | | | | Resolves #27497 Reviewed-by: Shane Lontis <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27581) (cherry picked from commit 8a9e0d0f499a288cf3363668870806d5e7be3924)
* crypto/evp: compensate for providers not adding error queue entries for ↵Dr. David von Oheimb2025-05-201-1/+7
| | | | | | | | | | keymgmt, sigver, and asymcipher Reviewed-by: Nicola Tuveri <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27367) (cherry picked from commit 72351b0d18078170af270418b2d5e9fc579cb1af)
* Fix SSL_{set1,add1}_host() handling of host name/IP address and related ↵Dr. David von Oheimb2025-05-061-2/+2
| | | | | | | | | | documentation Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27457) (cherry picked from commit 1eee02d3e710e01d864c37708f64e83511627e28)
* Ensure that our fips internal provider is always loadedMatt Caswell2025-04-301-0/+3
| | | | | | | | | | | | | The fips provider has an internal provider. In some circumstances we could end up trying to find it, but failing because it hasn't been loaded yet. We just always ensure it is loaded early to avoid this. Reviewed-by: Viktor Dukhovni <[email protected]> Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27408) (cherry picked from commit 6ff4c1d87468fdd18deeebbb01fbf049bd6cec1f)
* ossl_json_f64() seems to be unused, remove it to avoid libm dependencysashan2025-04-291-3/+0
| | | | | | | | Reviewed-by: Paul Dale <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27434) (cherry picked from commit 0e418628998d0337599643c1e4054c60e5f21ec4)
* Fix errors on SSL_accept() and SSL_get_error()Matt Caswell2025-04-241-2/+2
| | | | | | | | | | | | | | | | | | | Calling SSL_accept() was raising two errors on the stack if you passed the wrong object type. Similarly SSL_get_error() was adding an error to the stack if the wrong object type was passed and returning the wrong result. We also ensure SSL_set_accept_state() and SSL_set_connect_state() don't raise spurious errors since these are void functions. Fixes #27347 Fixes #27348 Reviewed-by: Saša Nedvědický <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27351) (cherry picked from commit cb5bb8916fa0e044e6658c8b3db6d7c672cb25fe)
* hashfunc: add stddef.h includeGerd Hoffmann2025-04-151-0/+1
| | | | | | | | | | | | | | size_t is declared in stddef.h, so include the header file to make sure it is available. Fixes build on UEFI. Signed-off-by: Gerd Hoffmann <[email protected]> Reviewed-by: Saša Nedvědický <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Matt Caswell <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27284) (cherry picked from commit 44e9c5a3edd199ed7d7fe427fe0e1ef76dc52663)
* Copyright year updatesopenssl-machine2025-03-252-2/+2
| | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> Release: yes
* Move the Handshake read secret change earlier in the process for QUIC 0-RTTMatt Caswell2025-03-201-0/+2
| | | | | | | | | | | | | | | | | 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 <[email protected]> Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27101) (cherry picked from commit 95051052b319d346a8aa3d34d6105d683bb77294)
* Fix the use of CCM ciphersuites with QUIC TLS APIMatt Caswell2025-03-202-0/+3
| | | | | | | | | Reviewed-by: Neil Horman <[email protected]> Reviewed-by: Tim Hudson <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from https://github.com/openssl/openssl/pull/27091) (cherry picked from commit 207cd5bb975f1cda542757b9695ac4e5bdb71576)
generated by cgit (git 2.51.2) at 2026-10-25 08:58:15 +0100