UX: list-keys option and less manual key(files) management #247
alxiong
started this conversation in
UX reports
Replies: 1 comment 1 reply
-
The absence of a keyring is intentional. Keys are cheap to make, so it's expected users will make new key pairs for each application/use, and explicitly refer to them as files. Avoiding GPG's implicit keyring semantics was an original goal of the design. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
similar to
gpg --list-keys
, would be nice if there's a canonical path to allage
's keys (e.g.~/.config/age/keys.txt
) and default delimiter would be added between keys when invokingage-keygen
so that a simple parsing and regex matching could supportlist-key
commandin general, key(file) management still involves a bit of manual work, which could be deliberately by design (idk) for simplicity or maybe other reasons, but as a user, it will be great to not care about details like umask in warning message is confusing #75 .
(I guess I was used to the
ssh-keygen
way)Beta Was this translation helpful? Give feedback.
All reactions