New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crypto: enable NODE_EXTRA_CA_CERTS with BoringSSL #52217
crypto: enable NODE_EXTRA_CA_CERTS with BoringSSL #52217
Conversation
Review requested:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This increases the number of #endif
directives without changing the number of #if
directives. You'll need to split the existing #if ... && ...
into two separate directives in order to use separate #endif
directives for the two conditions.
@tniessen oops, forgot to push that 😅 fixed. |
3b0f72c
to
248c632
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On a side note, the commit message does not adhere to the guidelines, I'd suggest crypto: enable NODE_EXTRA_CA_CERTS with BoringSSL
or something along those lines.
248c632
to
452d594
Compare
NODE_EXTRA_CA_CERTS
452d594
to
8904a61
Compare
Co-authored-by: Yagiz Nizipli <yagiz@nizipli.com>
Co-authored-by: Luigi Pinca <luigipinca@gmail.com>
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Landed in 28d68f3 |
As in title. It's possible for
NODE_EXTRA_CA_CERTS
to work in a BoringSSL context, so there's no need to include that in the guard. This allows Electron users to leverage it.