Skip to content

Commit

Permalink
crypto: BoringSSL can work with NODE_EXTRA_CA_CERTS
Browse files Browse the repository at this point in the history
  • Loading branch information
codebytere committed Mar 26, 2024
1 parent f1635f4 commit 3b0f72c
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/node.cc
Original file line number Diff line number Diff line change
Expand Up @@ -1174,7 +1174,7 @@ InitializeOncePerProcessInternal(const std::vector<std::string>& args,

// Ensure CSPRNG is properly seeded.
CHECK(crypto::CSPRNG(nullptr, 0).is_ok());

#endif // defined(OPENSSL_IS_BORINGSSL)
V8::SetEntropySource([](unsigned char* buffer, size_t length) {
// V8 falls back to very weak entropy when this function fails
// and /dev/urandom isn't available. That wouldn't be so bad if
Expand All @@ -1189,7 +1189,7 @@ InitializeOncePerProcessInternal(const std::vector<std::string>& args,
if (credentials::SafeGetenv("NODE_EXTRA_CA_CERTS", &extra_ca_certs))
crypto::UseExtraCaCerts(extra_ca_certs);
}
#endif // HAVE_OPENSSL && !defined(OPENSSL_IS_BORINGSSL)
#endif // HAVE_OPENSSL
}

if (!(flags & ProcessInitializationFlags::kNoInitializeNodeV8Platform)) {
Expand Down

0 comments on commit 3b0f72c

Please sign in to comment.