Use BC for hmac calculation on the extended key class #1106
Conversation
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
|
hey @dangershony sorry just saw this PR, can I know why you need this? none of our supported platform seems to fall into this case. |
|
I was making a bIp39 tool in blazor wasm and I needed this change because some of the crypto apis are not yet supported with blazor (they might be in dotnet7) |
NicolasDorier
force-pushed
the
master
branch
from
d114a5d to
e4c0829
Compare
NicolasDorier
force-pushed
the
master
branch
2 times, most recently
from
725a14b to
bbcaf18
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seem the extended key type was missing the
NO_NATIVE_HMACSHA512