On Thu, 2009-01-01 at 10:24 -0500, Eric Christensen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Yesterday on the train, I converted part of the "Using GPG" portion of > the Security Guide. I get an error when I try to "make" the book now. > > The error is: > > junk after document element at line 11, column 0, byte 739: > </para> > </section> > <section > id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_GNOME"> > ^ > <title>Creating GPG Keys in GNOME</title> > <para> > at > /usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi/XML/Parser.pm > line 187 > make: *** [xml-en-US] Error 4 > > > I've compared the file to other files that I have and I can't see any > differences. Does anyone have any ideas? > > > Thanks, > Eric Christensen > E-Mail: sparks@xxxxxxxxxxxxxxxxx > GPG Key: BD0C14C1 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAklc4CkACgkQfQTSQL0MFME9DACgi4e0+tilap7jwCBAF60Oq2Sv > qcQAoNFpKTfM+P2BuCnpXvJMXjwGSh2p > =Ip0i > -----END PGP SIGNATURE----- > Sorry it took a while to reply. Attached is my patch, it shouts about the <pre> tag being possibly broken but completes and builds clean on my box. -Jason
Index: en-US/Using_GPG.wiki =================================================================== --- en-US/Using_GPG.wiki (revision 18) +++ en-US/Using_GPG.wiki (working copy) @@ -2,14 +2,17 @@ <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [ ]> +<chapter id="Encryption_Using_GPG"> +<title>Encryption Using GPG</title> + <section id="sect-Security_Guide-Encryption-Using_GPG"> <title>Using GNU Privacy Guard (GnuPG)</title> <para> GPG is used to identify yourself and authenticate your communications, including those with people you don't know. GPG allows anyone reading a GPG-signed email to verify its authenticity. In other words, GPG allows someone to be reasonably certain that communications signed by you actually are from you. GPG is useful because it helps prevent third parties from altering code or intercepting conversations and altering the message. </para> </section> -<section id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_GNOME"> - <title>Creating GPG Keys in GNOME</title> +<section id="sect-Security_Guide-Encryption-Using_GPG-Creating_Keys_in_GNOME"> + <title>Creating GPG Keys in GNOME</title> <para> Install the Seahorse utility, which makes GPG key management easier. From the main menu, select <code>System > Administration > Add/Remove Software</code> and wait for PackageKit to start. Enter <code>Seahorse</code> into the text box and select the Find. Select the checkbox next to the ''seahorse'' package and select ''Apply'' to add the software. You can also install '''Seahorse''' at the command line with the command <code>su -c "yum install seahorse"</code>. </para> @@ -105,17 +108,16 @@ <para> Finally, <code>gpg</code> generates random data to make your key as unique as possible. Move your mouse, type random keys, or perform other tasks on the system during this step to speed up the process. Once this step is finished, your keys are complete and ready to use: <pre> -pub 1024D/1B2AFA1C 2005-03-31 John Q. Doe (Fedora Docs Project) <jqdoe@xxxxxxxxxxx> +pub 1024D/1B2AFA1C 2005-03-31 John Q. Doe (Fedora Docs Project) jqdoe@xxxxxxxxxxx Key fingerprint = 117C FE83 22EA B843 3E86 6486 4320 545E 1B2A FA1C sub 1024g/CEA4B22E 2005-03-31 [expires: 2006-03-31] </pre> The key fingerprint is a shorthand "signature" for your key. It allows you to confirm to others that they have received your actual public key without any tampering. You do not need to write this fingerprint down. To display the fingerprint at any time, use this command, substituting your email address: -<pre> -gpg --fingerprint jqdoe@xxxxxxxxxxx -</pre>pre> +<code>gpg --fingerprint jqdoe@xxxxxxxxxxx</code>code> + Your "GPG key ID" consists of 8 hex digits identifying the public key. In the example above, the GPG key ID is 1B2AFA1C. In most cases, if you are asked for the key ID, you should prepend "0x" to the key ID, as in "0x1B2AFA1C". {{admon/warning|If you forget your passphrase, the key cannot be used and any data encrypted using that key will be lost.|}} @@ -132,3 +134,6 @@ * [http://en.wikipedia.org/wiki/Public-key_cryptography Wikipedia - Public Key Cryptography] * [http://computer.howstuffworks.com/encryption.htm HowStuffWorks - Encryption] +</para> +</section> +</chapter> \ No newline at end of file
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list mailing list fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
