feat: PEM identity#9
Open
alanshaw wants to merge 1 commit into
Open
Conversation
alanshaw
force-pushed
the
ash/feat/pem-identity
branch
from
0d6e112 to
dfdab85
Compare
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
1 participant
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.
Adds
identity.key_fileconfiguration and flag (--key-file) that specifies the file where the agent private key (PEM encoded, ed25519) can be read from.The private key is now separate from the delegation storage so that it can be managed appropriately (i.e. set file permissions).
The PR also adds a
guppy identity generatecommand that will generate a new key and encode it to PEM.It's currently not completely wired up, since the client still uses go-ucanto.
In the future we might want to add a
guppy initcommand or simply generate the key file and config automatically for the user