Skip to content

Add caveats section in the doc of crypto #3479

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.

Sign up for GitHub

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

Closed
shigeki wants to merge 7 commits into from
Closed

Add caveats section in the doc of crypto #3479

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
e4ef21e
doc: add caveats of algs and key size in crypto
Jul 27, 2015
875f6ab
change "more than" to "at least"
thinred Jul 27, 2015
3db5f4f
update getDiffieHellman docs
thinred Jul 27, 2015
bbe1076
docs: remove md5 and sha1 in crypto example
Jul 27, 2015
220a635
sha1 -> sha265
thinred Jul 27, 2015
a152cd9
revise the doc according to jasnell's comments
Oct 22, 2015
db5b6e2
revise the doc according to 2nd jasnell's comments
Oct 22, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
revise the doc according to jasnell's comments
  • Loading branch information
Shigeki Ohtsu committed Oct 22, 2015
commit a152cd999e738c73bb422ffeb18fa3e79a1bc51f
6 changes: 3 additions & 3 deletions doc/api/crypto.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -772,12 +772,12 @@ temporary measure.

The crypto module still supports some algorithms which are already
compromised. And the API also allows to use ciphers and hashes with a
Copy link
Member

@jasnell jasnell Oct 22, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"And the API also allows the use of ciphers and hashes with a" (replace to with the)

small key size that are consider to be weak for a safe use.
small key size that are considered to be too weak for safe use.

Users should take full responsibility for selecting the crypto
algorithm and its key size according to their security requirements.
algorithm and key size according to their security requirements.

The following descriptions only show some of recommendations to use
The following descriptions only show some recommendations to use
crypto module. See [NIST SP 800-131A] for details.

Copy link
Member

@jasnell jasnell Oct 22, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps something like, "Based on the recommendations of [NIST SP 800-131A]:" instead?

- MD5 and SHA-1 are no longer acceptable where collision resistance is
Expand Down