Prefer reading secrets.json to using pass show
I'm attempting to maintain a top-level secrets.json that defines all of the sensitive data that I'd like to version-control without exposing everything in cleartext to the world. To that end, I'm using `git secret`, which will use `gpg` to encrypt secrets.json everytime I call `git secret hide` and decrypt everytime I call `git secret reveal`. I'm going to try this until I don't like it anymore... if that day comes... I should write a blog post about my setup to solicit useful feedback and share my ideas with others.
This commit is contained in:
parent
392832a1ca
commit
17c68d654b
5 changed files with 14 additions and 8 deletions
|
@ -1 +1 @@
|
|||
secrets.json:9e05ae88de0df720ecc712b8e6bded3301bfd890cd13d0fb34d83bd37d14b594
|
||||
secrets.json:7d596a3ed16403040d89dd7e033a2af58e7aaabb6f246f44751b80a1863a2949
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue