openssl/include, branch feature/evp_skey

ecx: convert to using generated parameter decoding

2025-08-22T05:33:20Z

Reviewed-by: Tomas Mraz Reviewed-by: Shane Lontis (Merged from https://github.com/openssl/openssl/pull/28275)

lms: convert to using generated parameter decoding

2025-08-22T05:33:03Z

Reviewed-by: Tomas Mraz Reviewed-by: Shane Lontis (Merged from https://github.com/openssl/openssl/pull/28275)

slh-dsa: convert to using a generated decoder

2025-08-22T05:33:03Z

Reviewed-by: Tomas Mraz Reviewed-by: Shane Lontis (Merged from https://github.com/openssl/openssl/pull/28275)

Make SSL_poll() and SSL_shutdown() better friends

2025-08-21T12:43:03Z

Current QUIC stack may leave connection monitored by SSL_poll() to stale during regular shutdown. The issue is triggered when ACK for client's FIN gets delayed. The sequeance of operations to trigger the stale of QUIC connection at client goes as follows: - application calls SSL_shutdown() on connection, the shutdown can not proceed, because bi-directional stream must be flushed. The client awaits ACK from server acknowledging reception of FIN on client's stream - the stream object gets destroyed, because application received all data from server. - application updates poll set and passes to SSL_poll() - ssl poll ticks the engine. Engine receives delayed ACK and marks stream as flushed. At this point the SSL_shutdown() operation may proceed given the application calls the SSL_shutdown(). However there is no mechanism to make SSL_poll() return so application is unable to proceed with its event loop where SSL_shutdown() may get called. This change introduces ossl_quic_channel_notify_flush_done() function which notifies channel when all streams are flushed (all FINs got ACKed). The first thing SSL_shudown() does it calls ossl_quic_stream_map_begin_shutdown_flush(). The function walks list of all streams attached to channel and notes how many streams is missing ACK for their FIN. In our test case it finds one such stream. Call to SSL_shutdown() returns and application destroys the SSL stream object and updates a poll set. SSL_poll() gets called. The QUIC stack (engine) gets ticked and reads data from socket. It processes delayed ACK now. The ACK-manager updates the stream notifying the server ACKs the FIN sent by client. The stream is flushed now. Thw shutdown_flush_done() for stream gets called on behalf of ACK manager. The shutdown_flush_done() does two things: - it marks stream as flushed - it decrements the num_shutdown_flush counter initialized be earlier call to ossl_quic_stream_map_begin_shutdown_flush() called by SSL_shutdown() The change here calls ossl_quic_channel_notify_flush_done() when num_shutdown_flush reaches zero. The ossl_quic_channel_notify_flush_done() then calls function ossl_quic_channel_notify_flush_done(), which just moves the state of the channel (connection) from active to terminating state. The change of channel state is sufficent for SSL_poll() to signal _EC event on connection. Once application receives _EC event on connection it should check the state of the channel/reason of error. In regular case the error/channel state hints application to call SSL_shutdown() so connection object can proceed with connection shutdown. The SSL_shutdown() call done now moves channel to terminated state. So the next call to SSL_poll() can signal _ECD which tells application it's time to stop polling on SSL connection object and destroy it. Fixes openssl/project#1291 Reviewed-by: Neil Horman Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/28116)

Add DetECDSA self test, signature is one byte shorter somehow

2025-08-20T23:58:55Z

Reviewed-by: Shane Lontis Reviewed-by: Neil Horman Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/28213)

Correct the synthetisized OPENSSL_VERSION_NUMBER

2025-08-13T04:05:18Z

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 Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/28230)

Remove OSSL_CRYPTO_ALLOC attribute from CRYPTO_*dup routines

2025-08-12T18:44:38Z

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 Reviewed-by: Neil Horman Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/28220)

Fix failure checking on rcu_read_lock

2025-08-09T13:22:13Z

during memfail testing: https://github.com/openssl/openssl/actions/runs/16794088536/job/47561223902 We get lots of test failures in ossl_rcu_read_lock. This occurs because we have a few cases in the read lock path that attempt mallocs, which, if they fail, trigger an assert or a silent failure, which isn't really appropriate. We should instead fail gracefully, by informing the caller that the lock failed, like we do for CRYPTO_THREAD_read_lock. Fortunately, these are all internal apis, so we can convert ossl_rcu_read_lock to return an int indicating success/failure, and fail gracefully during the test, rather than hitting an assert abort. Fixes openssl/project#1315 Reviewed-by: Paul Yang Reviewed-by: Dmitry Belyavskiy Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/28195)

crypto/mem.c: check for overflow in size calculation in CRYPTO_aligned_alloc

2025-08-08T16:22:10Z

The open-coded implementation performs addition of size and alignment, that may overflow. Signed-off-by: Eugene Syromiatnikov Reviewed-by: Saša Nedvědický Reviewed-by: Matt Caswell Reviewed-by: Paul Dale Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/28059)

crypto/mem.c: check the alignment for being a power of 2 in CRYPTO_aligned_alloc

2025-08-08T16:22:10Z

Otherwise the roundup calculation performed in the open-coded implementation may put the pointer out of bounds. Signed-off-by: Eugene Syromiatnikov Reviewed-by: Saša Nedvědický Reviewed-by: Matt Caswell Reviewed-by: Paul Dale Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/28059)