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

Remove parseKey, change ES256K and Ed25519 signers to Uint8Array only #224

Merged
merged 45 commits into from
Apr 4, 2022

Conversation

bshambaugh
Copy link
Contributor

This is an attempt to create a fix for:
#222

…ithms, add a not for secp256r1 support of in src/VerifierAlgorithm.common.ts
@mirceanis
Copy link
Member

This looks good!
I'll do a thorough review on Monday and merge it if there's nothing else to be done.

Very nice work!

Copy link
Member

@mirceanis mirceanis left a comment

Choose a reason for hiding this comment

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

Looks great!

Thank you for the contribution.

@mirceanis mirceanis merged commit 9132caf into decentralized-identity:master Apr 4, 2022
uport-automation-bot pushed a commit that referenced this pull request Apr 4, 2022
# [6.0.0](5.12.4...6.0.0) (2022-04-04)

### Bug Fixes

* remove parseKey, change ES256K and Ed25519 signers to Uint8Array only ([#224](#224)) ([9132caf](9132caf)), closes [#222](#222)

### BREAKING CHANGES

* The Signer classes exported by this library no longer accept private keys with string encodings, only `Uint8Array`. This reduces the potential ambiguity between different formats. Some utility methods are exported that allow users to convert some popular encodings to raw `Uint8Array`.
@uport-automation-bot
Copy link
Collaborator

🎉 This PR is included in version 6.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants