aboutsummaryrefslogtreecommitdiff
path: root/index.mdwn
diff options
context:
space:
mode:
authorrhatto@riseup.net <Silvio Rhatto>2014-04-06 22:22:50 -0300
committerrhatto@riseup.net <Silvio Rhatto>2014-04-06 22:22:50 -0300
commit0a1413d7d56314496d92b20db7ecfb114adef04f (patch)
tree43bc6c8bc6c284a6c43162994d7678a624c3336d /index.mdwn
parenta3eb9d5d4a9d3c06bdaa1b4c226b753fd8abcaec (diff)
downloadkeyringer-0a1413d7d56314496d92b20db7ecfb114adef04f.tar.gz
keyringer-0a1413d7d56314496d92b20db7ecfb114adef04f.tar.bz2
Index: more on recipient definitions
Diffstat (limited to 'index.mdwn')
-rw-r--r--index.mdwn6
1 files changed, 5 insertions, 1 deletions
diff --git a/index.mdwn b/index.mdwn
index f66df2c..c25b02f 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -66,7 +66,7 @@ Your next step is tell keyringer the OpenPGP key IDs to encrypt files to:
keyringer <keyring> recipients ls
Keyringer support multiple recipients in a per-folder style. Try it by
-creating a sample keyringer
+creating a sample recipient file:
keyringer <keyring> recipients edit closest-friends
@@ -77,6 +77,10 @@ Fill it with your friends key IDs. Now encrypt a secret just for then:
In other words, if keyringer finds a recipient file matching a given path,
it will use it instead of the global recipients file.
+You can even create recipient files with your friends' key IDs but without
+yours: then you shall be able to encrypt secrets for them that even you cannot
+access. Try to find an use case for that ;)
+
Each recipient list is defined in a file placed at `config/recipients` in your
keyring repository. Take care to add just trustable recipients.