Open
Conversation
Mic92
reviewed
Mar 3, 2026
| ## 2. Derive an age key: | ||
|
|
||
| ```bash | ||
| # Convert an ssh ed25519 key to an age key |
Owner
There was a problem hiding this comment.
Doesn't support ssh keys directly these days?
Author
There was a problem hiding this comment.
Line 20 there is slightly altered from the current README.
I don't actually know the answer based on the current documentation, which is partly why I started this update 😄. I appreciate the engagement here and would be glad to update this section if it doesn't fully reflect what the project supports. Is converting to an ssh key to an age key not strictly required?
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
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.
Hi all,
First off -- thanks for all of your work on this! I've been glad to have a seamless secrets management system that "just works" with my nix configs.
I did found the documentation to be a little hard to follow and ended up writing the guide in this pull request to make things more intuitive for me. In broad strokes, the change is to go away from a mono-README and break out instructions into singularly focused
docs/*.mdguides.docs/HowTo_[key-type].mdfilesdocs/InDepthUsage.md-- catchall for all of the useful docs in the second half of the mono-README; likely should break out into separate files in the same spirit as one guide per key