aboutsummaryrefslogtreecommitdiffstats
path: root/doc/gpg-agent.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/gpg-agent.texi')
-rw-r--r--doc/gpg-agent.texi14
1 files changed, 5 insertions, 9 deletions
diff --git a/doc/gpg-agent.texi b/doc/gpg-agent.texi
index 01b4227c6..17bd59c7a 100644
--- a/doc/gpg-agent.texi
+++ b/doc/gpg-agent.texi
@@ -326,10 +326,8 @@ Ignore requests to change change the current @sc{tty} respective the X
window system's @code{DISPLAY} variable. This is useful to lock the
pinentry to pop up at the @sc{tty} or display you started the agent.
-@item --ssh-support
-@itemx --ssh-support
-@opindex ssh-support
-@opindex ssh
+@item --enable-ssh-support
+@opindex enable-ssh-support
Enable emulation of the OpenSSH Agent protocol.
@@ -350,13 +348,11 @@ Once, a key has been added to the gpg-agent this way, the gpg-agent
will be ready to use the key.
Note: in case the gpg-agent receives a signature request, the user
-might need to be prompted for a passphrased, which is necessary for
+might need to be prompted for a passphrase, which is necessary for
decrypting the stored key. Since the ssh-agent protocol does not
contain a mechanism for telling the agent on which display/terminal it
-is running, gpg-agent's --ssh-support switch implies --keep-display
-and --keep-tty. This strategy causes the gpg-agent to open a pinentry
-on the display or on the terminal, on which it (the gpg-agent) was
-started.
+is running, gpg-agent's ssh-support will use the TTY or X display where
+gpg-agent has been started.
@end table