-
Notifications
You must be signed in to change notification settings - Fork 6
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
Ldproof Error #8
Comments
You probably have to install libsodium. Depending on your operating system, e.g.:
|
I'm using Windows OS. So Is there any specific software libs that have to be installed?. I tried to compile Key-format-java repository separately and its working fine. But when i try to sign some VC then it gives an error. |
I'm not sure how to install libsodium on Windows, maybe try to search for that information. Another option is to use the TinkEd25519Provider service instead of the NaClSodiumEd25519Provider service. Default services are configured here: https://github.com/danubetech/key-formats-java/tree/main/src/main/resources/META-INF/services You can override this in your own project by copying that file and setting a different service implementation (e.g. TinkEd25519Provider instead of NaClSodiumEd25519Provider). |
Thanks a lot @peacekeeper . TinkEd25519Provider works fine. |
Great..! If you don't have any other questions, can we close this issue? |
Ya definitely. Thanks. |
How to change in jar file |
@Muthurajj I'm sorry could you clarify your question? Maybe you could create a new issue in this repository? |
Hallo,
When I try touse ldproof to sign a VC i get the following error. I have included the dependancy of keyformats in my pom file. But still it does come. How to resolve it? Any ideas?
java.util.ServiceConfigurationError: com.danubetech.keyformats.crypto.provider.Ed25519Provider: Provider com.danubetech.keyformats.crypto.provider.impl.NaClSodiumEd25519Provider could not be instantiated
at com.danubetech.verifiablecredentials.VerifyCredentialTest.testcredential(VerifyCredentialTest.java:93)
The text was updated successfully, but these errors were encountered: