-
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
Add TPMKMS support #71
Merged
Merged
Changes from 17 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
0440a8a
Upgrade to latest `go.step.sm/crypto` with `TPMKMS` support
hslatman 9df0dcf
Add distinct case for attestation certificate chains
hslatman e70fbf9
Enable TPMKMS
hslatman 11986c7
Add `tpm` format for KMS attestation
hslatman 9079368
Upgrade to latest `go.step.sm/crypto` with TPMKMS support
hslatman 8829cd0
Make providing `--kms` a bit more forgiving
hslatman 78a205a
Add examples for `create` and `key` for TPMKMS
hslatman 40b9792
Add examples for `attest` and `certificate`
hslatman 96074a1
Extract logic for printing certificate to stdout
hslatman 8af6088
Upgrade to latest development version of `go.step.sm/crypto`
hslatman 658c068
Support printing certificate bundles in `step kms certificate`
hslatman f760ae9
Fix single certificate to import into YubiKey
hslatman 6cda4b6
Add examples for importing certificates into the TPMKMS
hslatman 72eabd6
Invert logic for showing attestation certificate chain vs. leaf
hslatman 968cd91
Add (experimental) support for creating new (attested) keys in `attest`
hslatman f3ee3b7
Upgrade to latest development version of `go.step.sm/crypto`
hslatman f74bb56
Upgrade to `v0.32.0` of `go.step.sm/crypto`
hslatman bc260c8
Improve help text for new key in `attest` subcommand
hslatman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably mentioning that this is for tpmkms only or just for new keys. You're also using always PKCS#1 so the RSA-PSS in the help seems unnecessary. We can adding it back if we add support for --new on other KMSs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in bc260c8.