-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
test: update certificates and private keys #22184
Conversation
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 9999 days for all of them to prevent this from happening again in near future. Fix: #22182
cc @MylesBorins @nodejs/crypto @bnoordhuis |
test/fixtures/keys/Makefile
Outdated
@@ -27,6 +27,7 @@ ca3-key.pem: | |||
ca3-csr.pem: ca3.cnf ca3-key.pem | |||
openssl req -new \ | |||
-extensions v3_ca \ | |||
-days 9999 \ |
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.
Gosh, this slipped my quick review. It isn't really necessary, since the days are set in ca3.cnf
.
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.
Should we remove it or just leave it?
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.
Removed.
@indutny no bueno test.parallel/test-crypto-sign-verify all failing https://ci.nodejs.org/job/node-test-commit-linux/20522/nodes=alpine-latest-x64/ |
Should be fixed now. |
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.
LGTM
we should fast track this as it is breaking lots of things
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.
😅
I wonder if we shouldn't look at potentially dynamically generating these every so often |
one last ci with sn extra 9... giving us 273 years to figure this out instead of 27 |
Ah yes, good ole Node.js 557.0.0 |
@indutny still getting failures on arm https://ci.nodejs.org/job/node-test-binary-arm/2608/RUN_SUBSET=5,label=pi3-docker/console |
|
@mhdawson and I dug in a bunch and it seems like the failures on arm are infra related... potentially during setup @rvagg can you dig into this? One more ci: https://ci.nodejs.org/job/node-test-pull-request/16265/ landing if green |
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.
Rubber-stamp LGTM if CI is green. +1 to fast-tracking
parallel/test-tls-server-verify still failing on Raspberry Pi... |
d82759a
to
3e39945
Compare
oops... I did the status file wrong re-running arm https://ci.nodejs.org/job/node-test-commit-arm-fanned/2721/ |
Diagnosis & fix nodejs/build#1432 |
Manually kicked off a node-daily-master now that this has landed just to make sure I didn't get confused and we still have a problem or something: https://ci.nodejs.org/job/node-daily-master/1247/ |
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 99999 days for all of them to prevent this from happening again in near future. PR-URL: #22184 Fixes: #22182 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
Custom suites failed to |
Unrelated flaky on LinuxONE, re-running: https://ci.nodejs.org/job/node-test-commit-linuxone/3652/ |
Custom suites passed. |
LinuxONE passed. |
Argh, the |
|
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 99999 days for all of them to prevent this from happening again in near future. PR-URL: #22184 Fixes: #22182 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 99999 days for all of them to prevent this from happening again in near future. PR-URL: #22184 Fixes: #22182 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 99999 days for all of them to prevent this from happening again in near future. PR-URL: #22184 Fixes: #22182 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
The certificates in test fixtures were set to expire in 999 days since
they were generated. That time has passed, and they have to be reissued.
Bump expiration time to 9999 days for all of them to prevent this from
happening again in near future.
Fix: #22182
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes