[Pkg-gnupg-commit] [gnupg1] 09/35: doc: Explain that gpg-preset-passphrase can't be used.
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Mon Aug 29 14:48:36 UTC 2016
This is an automated email from the git hooks/post-receive script.
dkg pushed a commit to branch master
in repository gnupg1.
commit bedcef635221398e7bbb5dc0df7b04e9a7ce97cf
Author: Werner Koch <wk at gnupg.org>
Date: Fri Apr 22 09:57:38 2016 +0200
doc: Explain that gpg-preset-passphrase can't be used.
--
---
doc/gpg.texi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/doc/gpg.texi b/doc/gpg.texi
index ae582d3..b770e0e 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -1640,7 +1640,9 @@ process. @option{--no-auto-check-trustdb} disables this option.
@opindex use-agent
Try to use the GnuPG-Agent. With this option, GnuPG first tries to
connect to the agent before it asks for a
-passphrase. @option{--no-use-agent} disables this option.
+passphrase. @option{--no-use-agent} disables this option. Note, that
+the tool @command{gpg-preset-passphrase}, which comes with GnuPG-2,
+cannot be used to preset a passphrase for this version of GnuPG.
@item --gpg-agent-info
@opindex gpg-agent-info
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-gnupg/gnupg1.git
More information about the Pkg-gnupg-commit
mailing list