feat: tedge cert create use HSM configuration
#3891
Draft
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.
TODO
Proposed changes
Make
tedge cert createcommand use the current HSM configuration, i.e. if we're currently using a PKCS11-based private key, sign the self-signed certificate using that key. Otherwise the certificate is broken as it's signed with a different private key that doesn't correspond to the public key info in the certificate.Normally
tedge cert createpersists to disk newly generated certificate and the private key, but now, if already existing PKCS11-based private key is used, the private key is not persisted (because it can't be).Types of changes
Paste Link to the issue
tedge cert createshould use HSM configuration #3890Checklist
just prepare-devonce)just formatas mentioned in CODING_GUIDELINESjust checkas mentioned in CODING_GUIDELINESFurther comments