Skip to content

Encrypt functionality with optional Keybase.io support  #29

Open

Description

@binlab

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

Activity

  1. LeSuisse commented on May 11, 2020

    @LeSuisse
    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions