net.corda.v5.crypto
The crypto package provides types used by services in net.corda.v5.application.crypto. The following types are available:
DigitalSignatureis used to identify the owner of the signing key used to create the signature.SecureHashis a cryptographically secure hash value, computed by a specified digest algorithm.SignatureSpecis a digital signature scheme.
For more information, see the documentation for the package in the Java API documentation.
Implementing Signature Schemes
Corda supports the following SignatureSpecs (signature schemes) for creating the following objects:
- SHA256withRSA
- SHA384withRSA
- SHA512withRSA
- RSASSA-PSS with SHA256
- RSASSA-PSS with SHA384
- RSASSA-PSS with SHA512
- RSASSA-PSS with SHA256 and MGF1
- RSASSA-PSS with SHA384 and MGF1
- RSASSA-PSS with SHA512 and MGF1
- SHA256withECDSA
- SHA384withECDSA
- SHA512withECDSA
- EdDSA
- SHA512withSPHINCS256
- SM3withSM2
- SHA256withSM2
- GOST3411withGOST3410
SignatureSpecService ensures that you do not pass the wrong signature spec for a signing-key type. It takes in a key and, optionally, a digest algorithm, and returns the appropriate default signature spec.
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.