We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The following test case indicates that it is supposed to be using a Uint8Array for the secret, but is in fact using a ArrayBuffer:
Uint8Array
ArrayBuffer
js-sha256/tests/hmac-test.js
Lines 94 to 99 in 189bb9b
The sha256_hmac test properly uses a Uint8Array.
The text was updated successfully, but these errors were encountered:
## v0.10.0 / 2023-08-30
bb8ae3a
### Fixed - Chrome bug by workaround. #40 - deprecated `new Buffer`, replace with `Buffer.from`. #34 - dependencies and security issues. #32, #36 ### Changed - TypeScript interface, secretKey can be bytes like message. #23, #25 - remove `eval` and use `require` directly. #18, #26
Updated TypeScript interface in v0.10.0. It also allows ArrayBuffer, so I close this.
Sorry, something went wrong.
No branches or pull requests
The following test case indicates that it is supposed to be using a
Uint8Array
for the secret, but is in fact using aArrayBuffer
:js-sha256/tests/hmac-test.js
Lines 94 to 99 in 189bb9b
The sha256_hmac test properly uses a
Uint8Array
.The text was updated successfully, but these errors were encountered: