Add signer method for pre-hashed data to allow tls/crypto to use openssl engines #120
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I have added a new method cal;led SignPKCS1v15Hash which allows the tls/crypto Signer method to use an openssl engine to sign data. A TPM (Trusted Platform Module) can then be used with Go code, using the library from here
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/openssl_tpm2_engine.git
There is also a function LoadPrivateKeyFromPEMForEngine which loads the engine with the reference to the private key.