4 ms·
I've been using `pass` for a very long time, and in combination with dmenu or rofi, it has proven to improve my workflow accessing passphrases a lot. For 'team
by miduil 10y ago
I've been using `pass` for a very long time, and in combination with dmenu or rofi, it has proven to improve my workflow accessing passphrases a lot.
For 'teams' (and serv{er, ices}) I've started implementing some stuff via. vault-project [0]. The project looks really promising, sadly never got up-voted on HN so far.
The basic concept of vault is a centralized storage of secrets, managed via. Access-Control-Lists (ACLs) and accessible via. REST.
Because the secrets are only accessible from a single point, you'll also have an overview of who did access which secret (called audit log). It's also possible to implement replacing all necessary secrets whenever someone has left/changed the group that got access to the secrets.
Vault also makes integration in certain provisioning tools possible (though, that's something you need to spend more development in).
Vault provides many database-backends [1], but also various other things (like ssh [2]).
Other things for managing secrets are:
- keywhiz: https://square.github.io/keywhiz/single_page.html https://square.github.io/keywhiz/single_page.html
- keyringer: https://keyringer.pw https://keyringer.pw
[0]: https://www.vaultproject.io/ https://www.vaultproject.io/
[1]: https://www.vaultproject.io/docs/secrets/index.html https://www.vaultproject.io/docs/secrets/index.html
[2]: https://www.vaultproject.io/docs/secrets/ssh/index.html https://www.vaultproject.io/docs/secrets/ssh/index.html
- riffic 10y agoHashicorp's Vault is highly regarded in the DevOps community.
- MetalMatze 10y agoYes. Vault is awesome and we're planning to use Vault ourselves. However Vault is mostly meant for machines to read the secrets and gopass is designed for humans.