You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0e87576
Browse filesBrowse the repository at this point in the historyBrowse files
BoringSSL implements OPENSSL_zalloc and BN_secure_new and provides
compatible secure heap status stubs. Use the common code paths.
Remove ClientHello helpers left unused by the early callback migration
and require the fixed ML-KEM private-key import error.
Signed-off-by: Filip Skokan <[email protected]>
PR-URL: #65423
Backport-PR-URL: #65483
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Tim Perry <[email protected]>
// It should really only be ERR_OSSL_EVP_PRIVATE_KEY_WAS_NOT_SEED
111
-
// but BoringSSL is inconsistent between handling ML-KEM and ML-DSA
112
-
// Fixed in https://github.com/google/boringssl/commit/94c4c7f9e0eeeff72ea1ac6abf1aed5bd2a82c0c
0 commit comments