Add API for using crypto.Signer with SigningContext #89
+245
−57
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.
The main purpose of the pull request adds a
crypto.Signer
toSigningContext
to enable signing by an HSM. This change also enables signing with ECDSA keypairs.NewSigningContext
to construct aSigningContext
that holds acrypto.Signer
and the certificate chain and is mutually exclusive withX509KeyStore
SigningContext
has a non-nilKeyStore
, it uses that instead to maintain backwards compatibility and not break existing code.x509.Certificate
'sCheckSignature
method instead of the RSA public key to support validation of ECDSA signaturesNote: This is just a slightly updated version of https://github.com/russellhaering/goxmldsig/pull/44/files. Full credit deserves to go to @charredlot.