| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Load the certificate chain from the PFX file the same as we do it for a regular certificate chain. Fix: nodejs#4127
|
cc @nodejs/crypto |
Sorry, something went wrong.
|
Actually just added the test that demonstrates the problem, feel free to review it now ;) |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
s/editted/edited/
Sorry, something went wrong.
There was a problem hiding this comment.
Ack.
Sorry, something went wrong.
|
There was failure on CI FIPS bot, fixed in latest commit. Running CI again: https://ci.nodejs.org/job/node-test-pull-request/935/ |
Sorry, something went wrong.
|
Gosh, messed it up. New CI: https://ci.nodejs.org/job/node-test-pull-request/936/ |
Sorry, something went wrong.
|
CI seems to be green, failures are completely unrelated. |
Sorry, something went wrong.
There was a problem hiding this comment.
Can you add a CHECK_EQ(*issuer, nullptr) and maybe a CHECK_EQ(*cert, nullptr) while you're here?
Sorry, something went wrong.
There was a problem hiding this comment.
You are totally right. It needs something more complex though, since we don't prevent people from passing in both cert+key and pfx for TLS server.
Sorry, something went wrong.
|
@bnoordhuis PTAL, should be better now. |
Sorry, something went wrong.
|
erm @bnoordhuis or @nodejs/crypto : I need your LGTM ;) |
Sorry, something went wrong.
|
Anyone? |
Sorry, something went wrong.
There was a problem hiding this comment.
I realize it's not new code but I believe PEM_read_bio_X509_AUX() also registers an error, but with tag ERR_LIB_PEM, not ERR_LIB_SSL.
Sorry, something went wrong.
There was a problem hiding this comment.
I would keep it as it is right now, just because it may make this PR a semver-major. Let's reconsider it later.
Sorry, something went wrong.
|
Is it planned that this will be be included in 4.2.x as well as 5.x? The reason I ask is that I believe a side-effect of this change is to fix a memory leak which is relevant to production stability. I can raise an issue/PR against 4.2.x with a fix only for the memory leak if necessary. |
Sorry, something went wrong.
|
@paddybyers yep, it has lts-watch tag ;) |
Sorry, something went wrong.
I see, thanks :) |
Sorry, something went wrong.
Load the certificate chain from the PFX file the same as we do it for a regular certificate chain. Fix: nodejs#4127 PR-URL: nodejs#4165 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Load the certificate chain from the PFX file the same as we do it for a regular certificate chain. Fix: nodejs#4127 PR-URL: nodejs#4165 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
| Back | FazBrowse Home | New Git URL |
Load the certificate chain from the PFX file the same as we do it for a
regular certificate chain.
Fix: #4127