-
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
document how to use crypto.sign() for algorithm+digest combinations without named constants #6108
Closed
Closed
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -734,6 +734,28 @@ console.log(sign.sign(private_key, 'hex')); | |
// Prints the calculated signature | ||
``` | ||
|
||
A [`sign`][] instance can also be created by just passing in the digest | ||
algorithm name, in which case OpenSSL will infer the full signature algorithm | ||
from the type of the PEM-formatted private key, including algorithms that | ||
do not have directly exposed name constants, e.g. 'ecdsa-with-SHA256'. | ||
|
||
Example: signing using ECDSA with SHA256 | ||
|
||
```js | ||
const crypto = require('crypto'); | ||
const sign = crypto.createSign('sha256'); | ||
|
||
sign.update('some data to sign'); | ||
|
||
const privateKey = '-----BEGIN EC PRIVATE KEY-----\n' + | ||
'MHcCAQEEIF+jnWY1D5kbVYDNvxxo/Y+ku2uJPDwS0r/VuPZQrjjVoAoGCCqGSM49\n' + | ||
'AwEHoUQDQgAEurOxfSxmqIRYzJVagdZfMMSjRNNhB8i3mXyIMq704m2m52FdfKZ2\n' + | ||
'pQhByd5eyj3lgZ7m7jbchtdgyOF8Io/1ng==\n' + | ||
'-----END EC PRIVATE KEY-----\n', | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. s/,/;/ |
||
|
||
console.log(sign.sign(private_key).toString('hex')); | ||
``` | ||
|
||
### sign.sign(private_key[, output_format]) | ||
|
||
Calculates the signature on all the data passed through using either | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Either update this const name to be
private_key
for consistency, or update the one passed intosign()
below.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 be camelcase for javascript, so the other should be fixed.
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.
You are correct that it should be camelCase, but the rest of the references in the doc use lower_case, so, I agree that consistency with the existing examples wins.