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

feat: verify creds signed with Ed25519VerificationKey2020 #3244

Merged
merged 2 commits into from
Sep 19, 2024

Conversation

dbluhm
Copy link
Member

@dbluhm dbluhm commented Sep 19, 2024

This PR adds support for verifying JSON-LD Credentials using a verification method of type Ed25519VerificationKey2020.

I'm not thrilled about this approach but I think it's the least disruptive change possible right now. Less disruptive seems like a good idea given @PatStLouis work on supporting VC-DI is already underway.

Sidebar, Patrick, hopefully the VC-DI and VCDM 2.0 implementation handles working with verification methods better than the original LDP-VC code does 😅 Working on a verification method that has been framed does not feel right.

@dbluhm dbluhm force-pushed the feature/ed25519-verification-key-2020 branch from 1ebab88 to 986d9a3 Compare September 19, 2024 03:09
@dbluhm
Copy link
Member Author

dbluhm commented Sep 19, 2024

I would rather be able to do something like this code in the didcomm-messaging-python library:

https://github.com/Indicio-tech/didcomm-messaging-python/blob/a0f6b88d39b90552d1a639334b71cb44ce07634e/didcomm_messaging/crypto/backend/askar.py#L76-L108

@PatStLouis
Copy link
Contributor

sorry for my confusion but can't aca-py already do this?

Copy link
Contributor

@jamshale jamshale left a comment

Choose a reason for hiding this comment

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

Changes look good and make sense, but I don't have much knowledge of the crypto verification method stuff so I will defer to other reviewers.

@dbluhm
Copy link
Member Author

dbluhm commented Sep 19, 2024

sorry for my confusion but can't aca-py already do this?

The Ed25519Signature2020 is supported for issuance and verification but only if used with an Ed25519VerificationKey2018, as it turns out. I thought the same before I ran into the problem while doing some interop testing.

@dbluhm dbluhm force-pushed the feature/ed25519-verification-key-2020 branch from 155bc95 to 840d3ee Compare September 19, 2024 17:44
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
@dbluhm dbluhm force-pushed the feature/ed25519-verification-key-2020 branch from 840d3ee to fcad023 Compare September 19, 2024 20:12
@dbluhm dbluhm merged commit e50fb6c into hyperledger:main Sep 19, 2024
10 checks passed
Copy link

sonarcloud bot commented Sep 19, 2024

@dbluhm dbluhm deleted the feature/ed25519-verification-key-2020 branch September 19, 2024 21:59
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.

3 participants