-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
gopass vs hashicorp vault #7
Comments
Short Anwser: Vault is for machines while gopass is for humans. Will add a longer answer to the README or the FAQ. |
This project looks super cool. We are often asked if Vault can do the types of things that gopass does and our general answer is "not really what Vault is meant for". Glad to have another neat project we can point people to in these cases! |
Vault would be an awesome backend for gopass, to compete with 1Password for Teams for example. Vault can have much more detailed permission rules and also has audit logs on who accessed what/when. Which is much harder or impossible to do with git repos. |
We are actually already planning on supporting different backends. Vault could make sense as an gopass backend. |
I'd also think that gopass could be used as the source of truth for secrets put into vault. If you're using a database backend and need to mount it in vault the credentials you give to vault could be stored in gopass. |
Yep, or your Vault token, or or or. |
While I see some similarities, what are the main differences ?
The text was updated successfully, but these errors were encountered: