Your message dated Sat, 26 Jan 2008 23:15:24 -0500
with message-id <[email protected]>
has caused the Debian Bug report #461980,
regarding gnupg-agent: manpage typos
to be marked as having been forwarded to the upstream software
author(s) [email protected]
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
(forw) Bug#461980: gnupg-agent: manpage typos
Sat, 26 Jan 2008 23:15:24 -0500
The attached patch fixes a number of spelling errors in the gpg-agent
manpage contributed by a Debian user.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461980#10 contains an
additional patch to fix some spelling errors.
Please keep the Cc line when replying to this mail.
Eric Dorland <[email protected]>
ICQ: #61138586, Jabber: [email protected]
--- Begin Message ---
Bug#461980: gnupg-agent: manpage typos
Mon, 21 Jan 2008 15:05:29 -0500
Note also that use of "respective" seems wrong. The closest I can
think of is "with respect to", but I'm not sure.
+++ /tmp/gpgent.1.gz.975 2008-01-21 15:03:33.000000000 -0500
@@ -1,4 +1,4 @@
-.TH GPG-AGENT 1 2008-01-02 "GnuPG 2.0.8" "GNU Privacy Guard"
+.TH GPG-AGENT 1 2008-01-21 "GnuPG 2.0.8" "GNU Privacy Guard"
\- Secret key management for GnuPG
@@ -96,7 +96,7 @@
Commands are not distinguished from options execpt for the fact that
-only one one command is allowed.
+only one command is allowed.
@@ -183,26 +183,26 @@
Select the debug level for investigating problems. \fIlevel\fR may be
no debugging at all.
some basic debug messages
more verbose debug messages
even more detailed messages
all of the debug messages you can get
How these messages are mapped to the actual debugging flags is not
-specified and may change with newer releaes of this program. They are
+specified and may change with newer releases of this program. They are
however carefully selected to best aid in debugging.
@@ -265,9 +265,9 @@
Format the info output in daemon mode for use with the standard Bourne
-shell respective the C-shell . The default is to guess it based on the
+shell respective the C-shell. The default is to guess it based on the
environment variable \fBSHELL\fR which is in almost all cases
.B --write-env-file \fIfile\fR
@@ -313,25 +313,25 @@
.B --default-cache-ttl \fIn\fR
-Set the time a cache entry is valid to \fIn\fR seconds. The default are
+Set the time a cache entry is valid to \fIn\fR seconds. The default is
.B --default-cache-ttl-ssh \fIn\fR
Set the time a cache entry used for SSH keys is valid to \fIn\fR
-seconds. The default are 1800 seconds.
+seconds. The default is 1800 seconds.
.B --max-cache-ttl \fIn\fR
Set the maximum time a cache entry is valid to \fIn\fR seconds. After
-this time a cache entry will get expired even if it has been accessed
-recently. The default are 2 hours (7200 seconds).
+this time a cache entry will be expired even if it has been accessed
+recently. The default is 2 hours (7200 seconds).
.B --max-cache-ttl-ssh \fIn\fR
Set the maximum time a cache entry used for SSH keys is valid to \fIn\fR
-seconds. After this time a cache entry will get expired even if it has
-been accessed recently. The default are 2 hours (7200 seconds).
+seconds. After this time a cache entry will be expired even if it has
+been accessed recently. The default is 2 hours (7200 seconds).
@@ -361,8 +361,8 @@
pattern or even against a complete dictionary is not very effective to
enforce good passphrases. Users will soon figure up ways to bypass such
a policy. A better policy is to educate users on good security
-behavior and optional to run a passphrase cracker regularly on all
-users passphrases t catch the very simple ones.
+behavior and optionally run a passphrase cracker regularly on all
+users passphrases to catch the very simple ones.
.B --max-passphrase-days \fIn\fR
@@ -377,11 +377,11 @@
.B --pinentry-program \fIfilename\fR
Use program \fIfilename\fR as the PIN entry. The default is installation
-dependend and can be shown with the \fB--version\fR command.
+dependent and can be shown with the \fB--version\fR command.
.B --pinentry-touch-file \fIfilename\fR
-By default the file name of the socket gpg-agent is listening for
+By default the filename of the socket gpg-agent is listening for
requests is passed to Pinentry, so that it can touch that file before
exiting (it does this only in curses mode). This option changes the
file passed to Pinentry to \fIfilename\fR. The special name
@@ -393,7 +393,7 @@
.B --scdaemon-program \fIfilename\fR
Use program \fIfilename\fR as the Smartcard daemon. The default is
-installation dependend and can be shown with the \fB--version\fR
+installation dependent and can be shown with the \fB--version\fR
@@ -410,7 +410,7 @@
named `\fIS.gpg-agent\fR', located in the home directory, and not create
a random socket below a temporary directory. Tools connecting to
\fBgpg-agent\fR should first try to connect to the socket given in
-environment variable \fIGPG_AGENT_INFO\fR and the fall back to this
+environment variable \fIGPG_AGENT_INFO\fR and then fall back to this
socket. This option may not be used if the home directory is mounted as
a remote file system. Note, that \fB--use-standard-socket\fR is the
default on Windows systems.
@@ -435,7 +435,7 @@
-Ignore requests to change change the current \fBtty\fR respective the X
+Ignore requests to change the current \fBtty\fR respective the X
window system's \fBDISPLAY\fR variable. This is useful to lock the
pinentry to pop up at the \fBtty\fR or display you started the agent.
@@ -458,7 +458,7 @@
the newly received key and storing it in a gpg-agent specific
-Once, a key has been added to the gpg-agent this way, the gpg-agent
+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
@@ -467,7 +467,7 @@
mechanism for telling the agent on which display/terminal it is running,
gpg-agent's ssh-support will use the TTY or X display where gpg-agent
has been started. To switch this display to the current one, the
-follwing command may be used:
+following command may be used:
@@ -601,12 +601,12 @@
This file is used when support for the secure shell agent protocol has
been enabled (see: [option --enable-ssh-support]). Only keys present
in this file are used in the SSH protocol. The \fBssh-add\fR tool
-y be used to add new entries to this file; you may also add them
+may be used to add new entries to this file; you may also add them
manually. Comment lines, indicated by a leading hash mark, as well as
-empty lines are ignored. An entry starts with optional white spaces,
+empty lines are ignored. An entry starts with optional whitespace,
followed by the keygrip of the key given as 40 hex digits, optionally
followed by the caching TTL in seconds and another optional field for
-arbitrary flags. A \fB!\fR may be prepended to the keygrip to
+arbitrary flags. The keygrip may be prefixed with a \fB!\fR to
disable this entry.
The follwoing example lists exactly one key. Note that keys available
@@ -632,7 +632,7 @@
Note that on larger installations, it is useful to put predefined
files into the directory `\fI/etc/skel/.gnupg/\fR' so that newly created
users start up with a working configuration. For existing users the
-a small helper script is provied to create these files (see: [addgnupghome]).
+a small helper script is provided to create these files (see: [addgnupghome]).
@@ -646,7 +646,7 @@
-This signal flushes all chached passphrases and if the program has been
+This signal flushes all cached passphrases and if the program has been
started with a configuration file, the configuration file is read again.
Only certain options are honored: \fBquiet\fR, \fBverbose\fR,
\fBdebug\fR, \fBdebug-all\fR, \fBdebug-level\fR, \fBno-grab\fR,
Description: Text document
--- End Message ---
--- End Message ---