Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encrypt functionality with optional Keybase.io support #29

Open
binlab opened this issue May 10, 2020 · 1 comment
Open

Encrypt functionality with optional Keybase.io support #29

binlab opened this issue May 10, 2020 · 1 comment

Comments

@binlab
Copy link

binlab commented May 10, 2020

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

@LeSuisse
Copy link
Owner

Hi,

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.

What problems are you trying to solve?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants