You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Encrypt functionality with optional Keybase.io support #29
If I'm correct, here is missed the command to encrypt. Do you have some plans to add it? It would be great to have it in one place with an optional possibility to use Keybase.io (like in this https://www.vaultproject.io/docs/concepts/pgp-gpg-keybase) or any other public available keys
Indeed the endpoint gpg/encrypt/:name has not been implemented because I did not have a use case for it and because in a situation where the user deals with the encryption and decryption process via Vault, it is preferable to use the transit secrets engine and stay away from PGP.
Activity
LeSuisse commentedon May 11, 2020
Hi,
Indeed the endpoint
gpg/encrypt/:namehas not been implemented because I did not have a use case for it and because in a situation where the user deals with the encryption and decryption process via Vault, it is preferable to use the transit secrets engine and stay away from PGP.What problems are you trying to solve?