-
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
Add tests for PKCS#8 private keys #26898
Conversation
66f3032
to
57fd106
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.
LGTM, thanks for picking this up!
test/parallel/test-crypto-rsa-dsa.js
Outdated
|
||
assert.strictEqual(verify.verify(dsaPubPem, signature, 'hex'), true); | ||
|
||
// Test the legacy 'DSS1' name. |
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'd be okay with dropping this, that's already checked around line 250.
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.
In my curious, is DSS1 same as SHA-1? 🤔
I found following line in Node.js Project but I couldn't find what happened historically about the relationship between DSS1 and SHA-1 from Google search.
Line 4459 in b4f58c2
// Historically, "dss1" and "DSS1" were DSA aliases for SHA-1 |
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.
DSS1 stands for DSA (Digital Signature Algorithm) with SHA-1 as the hash function. It's a long-deprecated (and now removed) openssl synonym from when openssl conflated public key algorithms with their hash functions.
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 see. Thanks 👍 👍 👍
@sasurau4 the problem about the test suite can be circumvented by running the tests directly with: |
@BridgeAR The tests succeeded when I ran |
@tniessen I fixed pointed out. Thanks for your review 👍 |
Landed in 85546c2. |
I added tests for unencrypted PKCS#8 private keys.
I generated the test PKCS#8 private keys by converting
test_rsa_privkey,pem
andtest_dsa_privkey.pem
byopenssl
command.Refs: #24928
I ranmake -j4 test
command, but failed.detailed error log
My environment is Ubuntu 18.04.2 LTS and succeeded when I ranmake test-only
command.Please help me🙏Updated: solved the above problem.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes