From 0b8c3df70b193c28c2d5a050735adace3fb60531 Mon Sep 17 00:00:00 2001 From: Tom Limoncelli Date: Thu, 5 Jul 2018 08:26:19 -0700 Subject: [PATCH] Linked setting up of GPG key (#260) --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index fe38dc1..48c5c0d 100644 --- a/README.md +++ b/README.md @@ -51,7 +51,11 @@ Rather than one GPG passphrase for all the files, each person with access has th Automated processes often need access to all the decrypted files. This is easy too. For example, suppose Git is being used for Puppet files. The master needs access to the decrypted version of all the files. Simply set up a GPG key for the Puppet master (or the role account that pushes new files to the Puppet master) and have that user run `blackbox_postdeploy` after any files are updated. Getting started is looks like this. -First, `cd` into a Git, Mercurial, Subversion +First, if you don't have a GPG key, set it up using instructions +such as: +[Set up GPG key](https://help.github.com/articles/generating-a-new-gpg-key/). +Now you are ready to go. +`cd` into a Git, Mercurial, Subversion or Perforce repository and run `blackbox_initialize`. After that, if a file is to be encrypted, run `blackbox_register_new_file` and you are done. Add and remove keys with `blackbox_addadmin` and