aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.rst
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2014-07-15 17:40:16 -0400
committerJoey Hess <joey@kitenet.net>2014-07-15 17:40:16 -0400
commit802b0d7f6ee48a0bf41625a3b9f33e545f8e5259 (patch)
tree7d55430ff03e7d6322c73eeb958902c171149ec9 /README.rst
parentce32004ddc44fbd565b96a3cb351a88640268972 (diff)
parent5dcc77f507d497fe4023e94a47b6a7a1f1146bce (diff)
downloadgit-remote-gcrypt-802b0d7f6ee48a0bf41625a3b9f33e545f8e5259.tar.gz
Merge branch 'master' into dgit/sid
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst12
1 files changed, 12 insertions, 0 deletions
diff --git a/README.rst b/README.rst
index fedd6b0..ba06259 100644
--- a/README.rst
+++ b/README.rst
@@ -60,6 +60,17 @@ The following ``git-config(1)`` variables are supported:
The ``gcrypt-participants`` setting on the remote takes precedence
over the repository variable ``gcrypt.participants``.
+``remote.<name>.gcrypt-publish-participants``
+ ..
+``gcrypt.publish-participants``
+ By default, the gpg key ids of the participants are obscured by
+ encrypting using `gpg -R`. Setting this option to `true` disables
+ that security measure.
+
+ The problem with using `gpg -R` is that to decrypt, gpg tries each
+ available secret key in turn until it finds a usable key.
+ This can result in unncessary passphrase prompts.
+
``remote.<name>.gcrypt-signingkey``
..
``user.signingkey``
@@ -68,6 +79,7 @@ The following ``git-config(1)`` variables are supported:
part of the participant list. You may use the per-remote version
to sign different remotes using different keys.
+
Environment Variables
=====================