FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

crypto: add sync methods, deprecate optional callbacks by jonathanong · Pull Request #189 · nodejs/node · GitHub

Repository navigation

crypto: add sync methods, deprecate optional callbacks - #189

Closed
jonathanong wants to merge 1 commit into
nodejs:v0.12from
jonathanong:crypto-async
Closed

jonathanong wants to merge 1 commit into
nodejs:v0.12from
jonathanong:crypto-async

Conversation

Copy link
Copy Markdown
Contributor

See #5

  • would you like me to add/change tests?
  • didn't bother disallowing callbacks in the sync version. after all this is about the public API. is that something you guys want?
  • want doc updates?
  • only changed .randomBytes() and .pseudoRandomBytes(). were there others?

Copy link
Copy Markdown
Contributor

I like this. @iojs/tc

Copy link
Copy Markdown
Contributor

+1

Copy link
Copy Markdown

Someone mentioned on another issue (I can't find right now) that we should consider aligning our crypto API with the WebCryptoAPI, specifically using getRandomValues. I think it was an excellent idea. Would this be the moment to consider it?

Copy link
Copy Markdown
Contributor

@ruimarinho Since 1.0.0-alpha is pushing for release, not right now. Though if there's not an official issue open asking for it then the issue should be created.

Copy link
Copy Markdown
Contributor

@jonathanong

only changed .randomBytes() and .pseudoRandomBytes(). were there others?

Yes, crypto.pbkdf2
Edit: I'm actually no so sure the callback is optional there.

Comment thread lib/crypto.js

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

“Please us” → “Please use” for these last two messages.

Copy link
Copy Markdown
Contributor Author

what's the status on this? if desired, i can rebase and reopen for v1.x

Copy link
Copy Markdown
Contributor

I'm pretty sure doc updates would be a necessity to merge this in, but I don't believe a rebase and reopen is necessary, as a contributor would merge it manually anyways (unless there are merge conflicts). I could be corrected on that.

syg pushed a commit to syg/node that referenced this pull request Jun 20, 2024
…s#186) (nodejs#189)

* Fix test-http-server-keepalive-req-gc

* Format

---------

Co-authored-by: Etienne Pierre-Doray <etipdoray@gmail.com>
Co-authored-by: Etienne Pierre-doray <etiennep@chromium.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants


Back | FazBrowse Home | New Git URL