Possible errata for GPH English edition
IIDA Yosiaki
y-iida@secom.co.jp
5 Mar 2000 17:11:23 +0900
Enjoy!
------------------------------------------------------------
--- c2.sgml~ Sun Dec 12 19:58:07 1999
+++ c2.sgml Fri Feb 18 14:34:15 2000
@@ -75,7 +75,7 @@
<para>
Britain used machines to guess keys during World War 2.
The German Enigma had a very large key space, but the British built
-speciailzed computing engines, the Bombes, to mechanically try
+specialized computing engines, the Bombes, to mechanically try
keys until the day's key was found.
This meant that sometimes they found the day's key within hours of
the new key's use, but it also meant that on some days they never
@@ -125,7 +125,7 @@
<!-- inlineequation -->
<emphasis>n(n-1)/2</emphasis> keys
are needed for each pair of people to communicate privately.
-This may be ok for a small number of people but quickly becomes unwieldly
+This may be ok for a small number of people but quickly becomes unwieldy
for large groups of people.
</para>
@@ -330,7 +330,7 @@
An algorithm that does work is to use a public key algorithm to
encrypt only the signature.
In particular, the hash value is encrypted using the signer's private
-key, and anbody can check the signature using the public key.
+key, and anybody can check the signature using the public key.
The signed document can be sent using any other encryption algorithm
including none if it is a public document.
If the document is modified the signature check will fail, but this
--- c4.sgml~ Sun Sep 19 09:58:44 1999
+++ c4.sgml Sun Feb 20 03:53:00 2000
@@ -15,7 +15,7 @@
drastically different security needs.
This complicates key management.
Socially, using &gnupg; is not strictly a personal decision.
-To use &gnupg effectively both parties communicating must use it.
+To use &gnupg; effectively both parties communicating must use it.
Finally, as of 1999, laws regarding digital encryption, and in particular
whether or not using &gnupg; is legal, vary from country to country and
is currently being debated by many national governments.
@@ -87,7 +87,7 @@
encrypted messages.
Protecting your private key prevents an attacker from simply using your
private key to decrypt encrypted messages and sign messages in your name.
-Correctly managing your web of trust prevents attackers from masquarading
+Correctly managing your web of trust prevents attackers from masquerading
as people with whom you communicate.
Ultimately, addressing these issues with respect to your own security
needs is how you balance the extra work required to use &gnupg; with
@@ -185,7 +185,7 @@
This may be inconvenient or impossible for you to do.
For example, you may not own your own machine and must use a computer
at work or school, or it may mean you have to physically disconnect
-your computer from your cable modem every time you want to use &gnupg;
+your computer from your cable modem every time you want to use &gnupg;.
</para>
<para>
@@ -209,7 +209,7 @@
a passphrase that is easier to guess than a random 128-bit key.
If the passphrase is a word, it is much cheaper to try all the
words in the dictionaries of the world's languages.
-Even if the word is permuted, &eg, k3wldood, it is still easier
+Even if the word is permuted, ⪚, k3wldood, it is still easier
to try dictionary words with a catalog of permutations.
The same problem applies to quotations.
In general, passphrases based on natural-language utterances
@@ -363,7 +363,7 @@
</para>
<para>
-Regardless of your own security needs, through, you should
+Regardless of your own security needs, though, you should
<emphasis>always be careful</emphasis> when signing other keys.
It is selfish to sign a key with just enough confidence in the key's
validity to satisfy your own security needs.
@@ -470,8 +470,8 @@
then it is not possible to sign the key yourself.
You must rely on the signatures of others and hope to find a chain
of signatures leading from the key in question back to your own.
-To have any chance of finding a chain, you must take the intitive
-and get your key signed by others outside of your intitial web of trust.
+To have any chance of finding a chain, you must take the initiative
+and get your key signed by others outside of your initial web of trust.
An effective way to accomplish this is to participate in key
signing parties.
If you are going to a conference look ahead of time for a key
@@ -485,7 +485,7 @@
<para>
Keep in mind, though, that this is optional.
-You have no obligation to either publically advertise your key or
+You have no obligation to either publicly advertise your key or
sign other people's keys.
The power of &gnupg; is that it is flexible enough to adapt to your
security needs whatever they may be.
--- c5.sgml~ Sat Oct 2 11:54:12 1999
+++ c5.sgml Sun Feb 27 11:35:14 2000
@@ -111,7 +112,7 @@
For example, the specification imposes three arbitrary trust levels
onto the user: none, marginal, and complete.
All degrees of trust felt by the user must be fit into one of those
-three cubby holes.
+three cubbyholes.
The key validation algorithm is also difficult for non-computer scientists
to understand, particularly the notions of “marginals needed” and
“completes needed”.
--- c6.sgml~ Sun Dec 19 01:25:19 1999
+++ c6.sgml Mon Feb 21 14:12:05 2000
@@ -89,7 +89,7 @@
<para>
This command creates a signature file that can be used
-to verify that the orginal file
+to verify that the original file
<replaceable class="parameter">filename</replaceable> has not
been changed.
Verification of the file using a detached signature is done using the
@@ -157,7 +157,7 @@
This command encrypts a document using a symmetric algorithm with
a key derived from a passphrase supplied by you during execution.
The key should be selected to make it difficult to randomly guess the key.
-To decrypt a document encrypted in this manner use the command.
+To decrypt a document encrypted in this manner use the command
<link linkend="decrypt"><option>decrypt</option></link>.
</para>
</refsect1>
@@ -279,7 +279,7 @@
<para>
This command generates a private/public key pair for use in encrypting,
decrypting, and signing of messages.
-You will br prompted for the kind of key you wish to create, the key
+You will be prompted for the kind of key you wish to create, the key
size, and the key's expiration date.
</para>
</refsect1>
@@ -327,7 +327,7 @@
</refnamediv>
<refsynopsisdiv>
<synopsis>
-send-keys <replaceable class="parameter">key</replaceable>
+<option>send-keys</option> <replaceable class="parameter">key</replaceable>
</synopsis>
</refsynopsisdiv>
@@ -815,7 +815,7 @@
<para>
Makes a signature on the current key.
-If th key is not yet signed by the default user or the user
+If the key is not yet signed by the default user or the user
given with the option
<link linkend="local-user"><option>local-user</option></link>,
the program displays the information of the key again, together with
@@ -844,7 +844,7 @@
<para>
Revoke a signature.
-Asks for each signature makde by a one of the private keys whether
+Asks for each signature made by a one of the private keys whether
a revocation certificate should be generated.
</para>
</refsect2>
@@ -1081,7 +1081,7 @@
<para>
This is a shortcut for the subcommand
-<link linkend="lsign">lsign</link>.
+<link linkend="lsign">lsign</link>
within the command
<link linkend="edit-key">edit-key</link>.
</para>
--- c7.sgml~ Mon Feb 7 00:27:05 2000
+++ c7.sgml Sat Feb 26 10:40:57 2000
@@ -78,7 +78,7 @@
<para>
This option takes the output from commands and prints it to
-the filename given to it as a parameter
+the filename given to it as a parameter.
</para> </refsect1>
</refentry>
@@ -545,7 +545,7 @@
load-extension
</refname>
<refpurpose>
-specifies an extension to load.
+specifies an extension to load
</refpurpose>
</refnamediv>
<refsynopsisdiv>
@@ -614,7 +614,7 @@
<para>
This only allows the import
- key validation will fail and you have to check
-the validity of the key my other means. This
+the validity of the key by other means. This
hack is needed for some German keys generated
with pgp 2.6.3in. You should really avoid using
it, because OpenPGP has better mechanics to do
@@ -885,7 +885,7 @@
yes
</refname>
<refpurpose>
-assume “yes&rdquo to most questions
+assume “yes” to most questions
</refpurpose>
</refnamediv>
<refsynopsisdiv>
@@ -911,7 +911,7 @@
no
</refname>
<refpurpose>
-assume “no&rdquo to most questions
+assume “no” to most questions
</refpurpose>
</refnamediv>
<refsynopsisdiv>
@@ -1021,7 +1021,7 @@
<para>
The filename <replaceable class="parameter">file</replaceable> may
also be prefixed with a scheme.
-The scheme “gnupg-ring:&rdquo makes the specified file the
+The scheme “gnupg-ring:” makes the specified file the
default keyring.
The scheme “gnupg-gdbm:” makes the specified file the
GDBM ring.
@@ -1534,9 +1534,9 @@
</title>
<para>
-Option arguments following this option are assumed to be encoded
-encoded in the character set specified with the option <link
-linkend="charset"><option>charset</option></link>.
+Option arguments following this option are assumed to be
+encoded in the character set specified with the option
+<link linkend="charset"><option>charset</option></link>.
This is the default behavior for &gpg;.
</para>
</refsect1>
@@ -1563,7 +1563,7 @@
</title>
<para>
-This options is processed before an attempt is made to open an options
+This option is processed before an attempt is made to open an options
file.
</para>
</refsect1>
@@ -1759,7 +1759,7 @@
</title>
<para>
-This option affects only the generation of secret keys
+This option affects only the generation of secret keys.
Output of option (comment?) packets is disabled since version 0.4.2
of &gnupg;.
</para>
@@ -2020,7 +2020,7 @@
The parameter <replaceable class="parameter">n</replaceable> sets the
maximum length of a chain of certified keys leading from an ultimately
trusted key to a key being validated.
-The default is 5
+The default is 5.
</para>
</refsect1>
</refentry>
@@ -2053,7 +2053,7 @@
supported digest algorithms.
Note that this option may violate the OpenPGP requirement that a
160-bit digest algorithm be used for DSA.
-For symmetric encryption, the default algorithm is RIPEMD-160
+For symmetric encryption, the default algorithm is RIPEMD-160.
</para>
</refsect1>
</refentry>
@@ -2112,7 +2112,7 @@
<para>
The parameter <replaceable class="parameter">name</replaceable> specifies
-the name of the digest algorithm to be used for mangling passphrases
+the name of the digest algorithm to be used for mangling passphrases.
The default algorithm is RIPEMD-160.
</para>
</refsect1>
@@ -2264,7 +2264,7 @@
This option is useful for cleartext signatures on patch files.
Messages signed this way should not be sent via email because all spaces
and line endings are hashed too.
-This option cannot be used for data which which has five dashes at the
+This option cannot be used for data which has five dashes at the
beginning of a line.
A special header line is used to tell &gnupg; that this option has
been used.
------------------------------------------------------------
--
iida