Signed-off-by: Erik Hollensbe <email@example.com>
|5 years ago|
|creds||5 years ago|
|keys||5 years ago|
|.gitignore||5 years ago|
|README.md||5 years ago|
|add_key||5 years ago|
|import_keys||5 years ago|
|list||5 years ago|
|rebuild||5 years ago|
|show||5 years ago|
|update||5 years ago|
Install gpg with your favorite tool, or ask some guy on freenode or slashdot to insult you unless you use theirs.
Make a key with
You'll see a line like this right above the line with your email address. I've bolded the part that is your public key id.
Export the public key to stdout with
gpg --export -a <public key id>.
Follow the steps below in
Adding your Key.
It's not a huge deal if you lose this thing, but it's kind of a pain in the ass if you do, so don't do that.
gpg is not in your path, you're gonna have a bad day. So go fix that
# list credentials $ ./list # show a specific credential $ ./show thing # mac users, break out your pbr: $ ./show thing | pbcopy # update or add a specific credential $ ./update thing < my_content # re-encrypt the whole thing with the entire set of keys $ ./rebuild
This will import your key, commit it and push it up.
$ ./add_key my_username < my_key.gpg
Then contact someone who already has decrypt access to encrypt everything.
gpg-agent and configure it - it will keep you from having to
enter your key password 800 times.
somewhere in an appropriate shell profile:
eval `gpg-agent --daemon`
And we're done! Will store your password the first time, not bug you about it
for a while. Nice for a lot of work in this repo, or using tools like
./rebuild that do a lot of decryption.