Replies: 2 comments
-
This issue overlaps with #56. |
Beta Was this translation helpful? Give feedback.
0 replies
-
API and CLI ways to inspect an encrypted file are indeed something we'll need to add at some point after v1.0.0. Tracking in #56.
In general, I do recommend that most projects pick a single recipient type, usually the native X25519 keys. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
To determine the key type of an encrypted secret, currently I am reading the file's header.
If you open an encrypted file in a text editor it will clearly show
-> ssh-rsa ...
,-> scrypt ...
, etc on the second line.Is this the proper way of determining a secret's key type (reading the raw header of the secret, and checking it) or is there a function within the spec/library to do this for me?
Or is it instead advised that I should enforce a specific key type for secrets in my projects?
Beta Was this translation helpful? Give feedback.
All reactions