Skip to content
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: crypto.privateEncrypt() padding list needs update #9609

Closed
mscdex opened this issue Nov 14, 2016 · 1 comment
Closed

doc: crypto.privateEncrypt() padding list needs update #9609

mscdex opened this issue Nov 14, 2016 · 1 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.

Comments

@mscdex
Copy link
Contributor

mscdex commented Nov 14, 2016

  • Version: all
  • Platform: n/a
  • Subsystem: doc

Currently crypto.privateEncypt() lists crypto.constants.RSA_PKCS1_OAEP_PADDING as a valid padding value, but it is actually only allowed for crypto.publicEncrypt() as far as encrypting goes. This value needs to simply be removed from that list in crypto.privateEncrypt()'s description.

@mscdex 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 Nov 14, 2016
@JungMinu
Copy link
Member

PR: #9611

addaleax pushed a commit that referenced this issue Nov 22, 2016
PR-URL: #9611
Fixes: #9609
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Sam Roberts <sam@strongloop.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
MylesBorins pushed a commit that referenced this issue Dec 20, 2016
PR-URL: #9611
Fixes: #9609
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Sam Roberts <sam@strongloop.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
MylesBorins pushed a commit that referenced this issue Dec 20, 2016
PR-URL: #9611
Fixes: #9609
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Sam Roberts <sam@strongloop.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
MylesBorins pushed a commit that referenced this issue Dec 21, 2016
PR-URL: #9611
Fixes: #9609
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Sam Roberts <sam@strongloop.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
MylesBorins pushed a commit that referenced this issue Dec 21, 2016
PR-URL: #9611
Fixes: #9609
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Sam Roberts <sam@strongloop.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants