crypto: remove obsolete BoringSSL shims and use available APIs - #65423
Open
panva wants to merge 3 commits into
Open
crypto: remove obsolete BoringSSL shims and use available APIs#65423panva wants to merge 3 commits into
panva wants to merge 3 commits into
Conversation
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 <panva.ip@gmail.com>
Use BoringSSL's current RSA and DH validation results instead of maintaining backend-specific prechecks and collapsing key errors. Report negotiated TLS groups and the documented zero security level through BoringSSL's compatibility APIs. Signed-off-by: Filip Skokan <panva.ip@gmail.com>
Collaborator
|
Review requested:
|
panva
added
the
commit-queue-rebase
nodejs-github-bot
added
lib / src
panva
added
dont-land-on-v22.x
pimterry
approved these changes
Aug 20, 2026
github-actions
Bot
removed
the
request-ci
This comment was marked as outdated.
This comment was marked as outdated.
panva
added
author ready
aduh95
reviewed
Aug 20, 2026
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use BoringSSL's current RSA and DH validation results instead of maintaining backend-specific prechecks and collapsing key errors.
Report negotiated TLS groups and the documented zero security level through BoringSSL's compatibility APIs.
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 since #64827 and require the fixed ML-KEM private-key import error.