Skip to content

crypto: remove arbitrary UTF16 restriction - #29795

Closed
addaleax wants to merge 2 commits into
nodejs:masterfrom
addaleax:no-crypto-utf16-restrictions
Closed

crypto: remove arbitrary UTF16 restriction#29795
addaleax wants to merge 2 commits into
nodejs:masterfrom
addaleax:no-crypto-utf16-restrictions

Conversation

@addaleax

Copy link
Copy Markdown
Member

Since 71f633a, this is no longer necessary.

Refs: #22622
Fixes: #29793

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Since 71f633a, this is no longer necessary.
Refs: nodejs#22622Fixes: nodejs#29793
@addaleaxaddaleax added crypto Issues and PRs related to the crypto subsystem. dont-land-on-v8.x labels Oct 1, 2019
@nodejs-github-botnodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. errors Issues and PRs related to JavaScript errors originated in Node.js core. labels Oct 1, 2019
@addaleaxaddaleax added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Oct 1, 2019
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Comment threaddoc/api/errors.md Outdated
Co-Authored-By: Colin Ihrig <cjihrig@gmail.com>
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@Trott

Trott commented Oct 3, 2019

Copy link
Copy Markdown
Member

Landed in 389969e

Trott pushed a commit that referenced this pull request Oct 3, 2019
Since 71f633a, this is no longer necessary.
Refs: #22622Fixes: #29793
PR-URL: #29795
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: David Carlier <devnexen@gmail.com>
@TrottTrott closed this Oct 3, 2019
@addaleax
addaleax deleted the no-crypto-utf16-restrictions branch October 3, 2019 21:03
BridgeAR pushed a commit that referenced this pull request Oct 9, 2019
Since 71f633a, this is no longer necessary.
Refs: #22622Fixes: #29793
PR-URL: #29795
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: David Carlier <devnexen@gmail.com>
@BridgeARBridgeAR mentioned this pull request Oct 10, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.c++Issues and PRs that require attention from people who are familiar with C++.cryptoIssues and PRs related to the crypto subsystem.errorsIssues and PRs related to JavaScript errors originated in Node.js core.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The digest function of the Crypto module's Hash object fails encoding hash in utf16le encoding

10 participants

@addaleax@nodejs-github-bot@Trott@jasnell@lpinca@targos@cjihrig@devnexen@BridgeAR@BethGriggs