openssl/pkcs11-provider, branch dependabot/github_actions/actions/setup-python-7

Update pkcs11-provider submodule (5dcc876)

2026-07-13T08:14:22Z

Signed-off-by: Ondrej Moris Reviewed-by: Dmitry Belyavskiy Reviewed-by: Igor Ustinov MergeDate: Mon Jul 13 08:14:30 2026 (Merged from https://github.com/openssl/openssl/pull/31907)

pkcs11-provider: update to latest version

2026-06-15T20:22:31Z

This fixes accidental version update in e2bd9f8c28 which is causing CI failure for pkcs11-provider tests. It needs to add xxd package that is used in the new hkdf test. Fixes: e2bd9f8c28c0 "ml_kem: return an error on catastrophic failure in decap" Reviewed-by: Neil Horman Reviewed-by: Eugene Syromiatnikov Reviewed-by: Milan Broz MergeDate: Mon Jun 15 20:23:25 2026 (Merged from https://github.com/openssl/openssl/pull/31522)

ml_kem: return an error on catastrophic failure in decap

2026-06-15T13:58:27Z

ML-KEM decapsulation applies implicit rejection by copying the failure key into the shared secret when the FO re-encryption check fails. This is correct for a syntactically valid but incorrect ciphertext, and must stay constant-time and ciphertext-dependent. However, the same path was also taken when hash_kr() or encrypt_cpa() failed outright, for example on a memory allocation failure inside EVP_DigestInit_ex(). In that case decap() copied the failure key and still returned success, so the caller derived a wrong shared secret with no error reported. For QUIC this produces a handshake that cannot converge: the derived keys diverge from the peer, packets fail to decrypt, and the connection stalls until it times out, with no diagnostic pointing at the real cause. These primitive failures are not dependent on the ciphertext, so reporting them as a hard error does not create a chosen-ciphertext oracle and does not weaken the constant-time implicit rejection that happens later via CRYPTO_memcmp() and constant_time_select_8(). Treat them the same way the existing kdf() failure is already treated, by raising an error and returning 0. Also fix the comment, which referred to hash_g() where the code actually calls hash_kr(). Reviewed-by: Bob Beck Reviewed-by: Tomas Mraz MergeDate: Mon Jun 15 13:58:32 2026 (Merged from https://github.com/openssl/openssl/pull/31432)

update pkcs11 submodule

2026-06-09T18:17:00Z

Reviewed-by: Saša Nedvědický Reviewed-by: Bob Beck Reviewed-by: Nikola Pajkovsky MergeDate: Tue Jun 9 18:17:30 2026 (Merged from https://github.com/openssl/openssl/pull/31018)

Update pkcs11-provider submodule (663dea3)

2025-10-03T17:09:42Z

Signed-off-by: Ondrej Moris Reviewed-by: Tomas Mraz Reviewed-by: Dmitry Belyavskiy Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/28716)

Update pkcs11-provider submodule

2025-05-20T19:29:14Z

Signed-off-by: Ondrej Moris Reviewed-by: Dmitry Belyavskiy Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/27602)

Update pkcs11-provider submodule (898b107)

2025-03-03T08:35:16Z

Signed-off-by: Ondrej Moris Reviewed-by: Dmitry Belyavskiy Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/26899)

test: Add external test for pkcs11-provider

2024-10-21T10:43:03Z

Reviewed-by: Dmitry Belyavskiy Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/25587)