-
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
doc: bad crypto.verify()
dsaEncoding description
#37454
Labels
crypto
Issues and PRs related to the crypto subsystem.
doc
Issues and PRs related to the documentations.
good first issue
Issues that are suitable for first-time contributors.
Comments
mscdex
added
crypto
Issues and PRs related to the crypto subsystem.
doc
Issues and PRs related to the documentations.
good first issue
Issues that are suitable for first-time contributors.
labels
Feb 20, 2021
I would like to work on this issue |
@HiroyukiYagihashi sorry i've already created a pr for this, you are welcome to review it |
What this issues? |
Hello there, |
This was referenced Apr 18, 2023
This was referenced Apr 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
crypto
Issues and PRs related to the crypto subsystem.
doc
Issues and PRs related to the documentations.
good first issue
Issues that are suitable for first-time contributors.
📗 API Reference Docs Problem
Location
crypto.verify()
Affected URL(s):
Description
The description of
dsaEncoding
uses the term "generated signature" which is a bit confusing when the function is actually verifying an existing signature and may be a copy-paste error fromcrypto.sign()
.submit a pull request.
The text was updated successfully, but these errors were encountered: