-
Notifications
You must be signed in to change notification settings - Fork 30k
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: move all TLS-PSK documentation to its section #35717
Conversation
I've also reworded some things and removed the phrase "identity must use UTF-8 encoding" since it doesn't seem to make sense, |
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.
Great idea
@mildsunrise can you please address the comments so this can land? |
My comments are non-blocking, so it's really just @lundibundi's one suggestion (which might also be non-blocking)? |
This needs a rebase. |
Landed in c3358aa |
PR-URL: #35717 Reviewed-By: Rich Trott <[email protected]>
PR-URL: nodejs#35717 Reviewed-By: Rich Trott <[email protected]>
PR-URL: nodejs#35717 Reviewed-By: Rich Trott <[email protected]>
PR-URL: #35717 Reviewed-By: Rich Trott <[email protected]>
PR-URL: #35717 Reviewed-By: Rich Trott <[email protected]>
The documentation on PSK is scattered in various places, I suggest we put it all in its section (and link to there).
PSK is a marginal feature and must be used with care, so I think it's better this way, and we avoid cluttering the
options
section with really long option entries.@nodejs/documentation @nodejs/crypto