GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||
GeezerVison is showing github.com — crypto: remove obsolete BoringSSL shims and use available APIs by panva · Pull Request #65423 · nodejs/node Conversation
Member
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.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactionsBoringSSL 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]> 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 <[email protected]>
Collaborator
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
pimterry
approved these changes
This comment was marked as outdated.
aduh95
reviewed
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as outdated.
|
There was an error while loading. Please reload this page.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@ ## main #65423 +/- ## ========================================== - Coverage 90.12% 90.12% -0.01% ========================================== Files 752 752 Lines 252325 252321 -4 Branches 47456 47464 +8 ========================================== - Hits 227407 227398 -9 + Misses 16217 16211 -6 - Partials 8701 8712 +11
🚀 New features to boost your workflow:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Landed in e573bd6...30fe871 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
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 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
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 <[email protected]> PR-URL: #65423 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
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: nodejs#65423 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
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 <[email protected]> PR-URL: nodejs#65423 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
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]>
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 <[email protected]> PR-URL: #65423 Backport-PR-URL: #65483 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Tim Perry <[email protected]>
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]>
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 <[email protected]> PR-URL: #65423 Backport-PR-URL: #65483 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Tim Perry <[email protected]>
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]>
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 <[email protected]> PR-URL: #65423 Backport-PR-URL: #65483 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Tim Perry <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.