-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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 link according to NIST bibliography #19593
Conversation
According to NIST SP 800 38D, this is the document the link orginally pointed to. Fixes: nodejs#17619
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 add a new available link for this?
@starkwang There is no "official" link anymore, NIST does not seem to provide the document anymore. IMO it is sufficient to provide the name of the document and the authors. |
// http://csrc.nist.gov/groups/ST/toolkit/BCM/documents/ | ||
// proposedmodes/gcm/gcm-revised-spec.pdf | ||
// Following test cases are from "The Galois/Counter Mode of Operation (GCM)" | ||
// by D. McGrew and J. Viega, published by the Natl. Inst. Stand. Technol. |
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.
National Institute of Standards and Technology
?
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.
Yeah... Natl. Inst. Stand. Technol.
is the abbreviation which is used in their own document, I just copied it. Personally, I would just write NIST, what do you prefer?
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.
NIST LGTM.
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 think NIST would be better.
Landed in ed0501f |
According to NIST SP 800 38D, this is the document the link orginally pointed to. Fixes: #17619 PR-URL: #19593 Reviewed-By: Weijia Wang <starkwang@126.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
According to NIST SP 800 38D, this is the document the link orginally pointed to. Fixes: #17619 PR-URL: #19593 Reviewed-By: Weijia Wang <starkwang@126.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
According to NIST SP 800 38D, this is the document the link orginally pointed to. Fixes: #17619 PR-URL: #19593 Reviewed-By: Weijia Wang <starkwang@126.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
According to Appendix E of NIST SP 800 38D, this is the document the link orginally pointed to.
Fixes: #17619
Checklist