nightmorph 07/07/16 03:00:25 Modified: gnupg-user.xml Log: Proper English, grammar, spelling, and some small GuideXML coding style fixes. No content change.
Revision Changes Path 1.42 xml/htdocs/doc/en/gnupg-user.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gnupg-user.xml?rev=1.42&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gnupg-user.xml?rev=1.42&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gnupg-user.xml?r1=1.41&r2=1.42 Index: gnupg-user.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gnupg-user.xml,v retrieving revision 1.41 retrieving revision 1.42 diff -u -r1.41 -r1.42 --- gnupg-user.xml 20 Feb 2007 22:07:04 -0000 1.41 +++ gnupg-user.xml 16 Jul 2007 03:00:25 -0000 1.42 @@ -1,10 +1,11 @@ <?xml version='1.0' encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gnupg-user.xml,v 1.41 2007/02/20 22:07:04 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gnupg-user.xml,v 1.42 2007/07/16 03:00:25 nightmorph Exp $ --> <guide link = "/doc/en/gnupg-user.xml"> -<title>GnuPG Gentoo user guide</title> +<title>GnuPG Gentoo User Guide</title> + <author title="Author"> <mail link="[EMAIL PROTECTED]">Gustavo Felisberto</mail> </author> @@ -159,12 +160,12 @@ <p> Now enter your key passphrase twice. It is a good idea to use a strong password. If someone ever gets hold of your private key and cracks your password, they -will be able to send messages signed by "you" making everyone believe the mails +will be able to send messages signed by "you", making everyone believe the mails were sent by you. </p> <p> -Then, GnuPG will generate your key. Moving the mouse or having a mp3 playing in +Next, GnuPG will generate your key. Moving the mouse or having a mp3 playing in the background will help speed up the process because it generates random data. </p> @@ -379,7 +380,7 @@ <p> You can also send other people's keys that you have signed to the keyserver. We could send Luis Pinto's key to the keyserver. This way someone who trusts -your key can use the signature that you have placed there to trust Luis' key. +your key can use the signature that you have placed there to trust Luis's key. </p> </body> @@ -391,7 +392,7 @@ <p> Now we are going to search for Gustavo Felisberto's key and add it to the keyring of John Doe (just in case you did not notice Gustavo Felisberto is the -author this guide :) ). +author this guide :)). </p> <pre caption="Searching keys from keyservers"> @@ -432,10 +433,10 @@ <body> <p> -There are cases, when working with certain applications, where you use your GPG -key very frequently, which means that you have to type your passphrase a lot of +Sometimes working with certain applications requires you to use your GPG key +very frequently, which means that you have to type your passphrase a lot of times. Several applications used to support a passphrase caching mechanism to -make life easier for users, this however disallowed sharing this cache across +make life easier for users. However, this disallowed sharing this cache across programs (how secure would that be?) and forced applications to reinvent the wheel over and over again. </p> @@ -593,9 +594,9 @@ <p> Another nice command is <c>gpg --refresh-keys</c>. This will contact the keyserver defined in the options file and refresh public keys in your local key -ring from there, searching for revoked keys, new id's, new signatures on keys. -You should probably run this once or twice a month so that if someone revokes -his key you will be notified. +ring from there, searching for revoked keys, new IDs, and new signatures on +keys. You should probably run this once or twice a month so that if someone +revokes his key you will be notified. </p> </body> @@ -610,14 +611,14 @@ <p> 95% of the time you will use GnuPG with email, signing/encrypting your outgoing -messages and reading signed/encrypted messages. So it is only fair that i talk +messages and reading signed/encrypted messages. So it is only fair that I talk about that first. </p> <p> There are two ways two sign/encrypt a email with GnuPG, the old way and the new way :). In the old way messages would appear in plain text, with no possible -formatting and attached files would be unsigned/unencrypted, here is an example +formatting and attached files would be unsigned/unencrypted. Here is an example of a message signed the old way: </p> @@ -637,7 +638,7 @@ </pre> <p> -Messages this way are no good in todays world, where we have nice GUI's and +Messages this way are no good in today's world, where we have nice GUIs and email readers that understand html. </p> @@ -645,7 +646,7 @@ To solve this an addition to the MIME (Multipurpose Internet Mail Extensions) was created. This adds a field to the email that tells the mail reader that the full content of the message is signed and/or encrypted. The problem with this -is that not all mail readers support this. And some even mess the content, +is that not all mail readers support this. And some even mess up the content; Microsoft's Outlook is famous for not working with this. </p> @@ -674,7 +675,7 @@ <p> Now you can see the key managing window. From here we see our good key for John Doe. The two trusted keys for Gustavo and Luis, and the untrusted key for Daniel -Robbins ( I still have not given him a call to check his fingerprint :) ). +Robbins (I still have not given him a call to check his fingerprint :)). </p> </body> @@ -772,17 +773,17 @@ <p> The concept of public key cryptography was originally devised by Whitfield Diffie and Martin Hellman in 1976. When I first heard the words "public key" and -"cryptography" in the same sentence back in '93 I tought to myself that it would -be impossible to do such a thing. In those days there was no Internet (well -there was, but not for me) so I went to the public library and asked for books -on Cryptography. I must say that I was 16 at the time so the clerk there looked -to me in astonishment and brought me a book for children on substitution cyphers -(those where you change a letter for another like the famous Caesar Cypher or -ROT-13 (Tragbb Ebpxf, naq lbh xabj vg vf tbbq orpnhfr lbh ner ernqvat guvf -qbp.), (emerge rotix if you cannot read the preceding text)). I was very upset -with this and started to search for more info. It is good to have mathematicians -in the family, because as soon as I talked to one of them I was introduced to a -new world. +"cryptography" in the same sentence back in '93 I thought to myself that it +would be impossible to do such a thing. In those days there was no Internet +(well there was, but not for me) so I went to the public library and asked for +books on Cryptography. I must say that I was 16 at the time so the clerk there +looked to me in astonishment and brought me a book for children on substitution +cyphers (those where you change a letter for another like the famous Caesar +Cypher or ROT-13 (Tragbb Ebpxf, naq lbh xabj vg vf tbbq orpnhfr lbh ner ernqvat +guvf qbp.), (<c>emerge rotix</c> if you cannot read the preceding text)). I was +very upset with this and started to search for more info. It is good to have +mathematicians in the family, because as soon as I talked to one of them I was +introduced to a new world. </p> <p> @@ -838,12 +839,12 @@ protocol. For even more info go to the public library and grab a copy of the <uri link="http://www.cacr.math.uwaterloo.ca/hac/";>"Handbook of Applied Cryptography"</uri> by Alfred J. Menezes, Paul C. van Oorschot and Scott A. -Vanstone, also this book is available online for free at the above site. +Vanstone. This book is also available online for free at the above site. </p> <p> One consequence of the above is that if you cypher a message to me, and you -loose the original uncypherd message you will no longer be able to retrieve it +loose the original uncyphered message you will no longer be able to retrieve it from the cyphered version. </p> @@ -865,14 +866,14 @@ when you cypher a message to me you sign it with your private key so that, when I receive it, I can first use your public key to check your signature and then use my private key to decypher the message. As you can see we could not do -that in the setup i described before. +that in the setup I described before. </p> <p> -Also very important, to sign messages you don't have to cypher them before. So -like that you can create messages that can be read by anyone, but that come with -your "branding". And if any single character is changed in the message it can -(and will) be detected. +It's also very important to sign messages so that you don't have to cypher them +beforehand. Now you can create messages that can be read by anyone, but that +come with your "branding". And if any single character is changed in the message +it can (and will) be detected. </p> </body> @@ -882,20 +883,20 @@ <body> <p> -But lets say that I have no previous contact with you until you send me a -message, how do I get your public key, and how do I really know it is yours? +But let's say that I have no previous contact with you until you send me a +message: how do I get your public key, and how do I really know it is yours? </p> <p> To solve this problem public Key Servers were created. When you create your key -pair (Public and Private key) you send your public key to the key server. After +pair (Public and Private key), you send your public key to the key server. After this everyone can retrieve your key from there. This solves the problem of finding the key. But how do I really know that that key is the author's key? For this another concept must be introduced, and that is key signing: </p> <p> -Key signing means that, if I have the public key of another person, and I know +Key signing means that if I have the public key of another person, and I know <e>for sure</e> that it is really that persons key (it is my personal friend, someone I know in real life, etc.) I can sign that public key and send it to keyservers, that way I am telling the world: "This key really belongs to the @@ -904,20 +905,20 @@ </p> <p> -This can sometimes be confusing so lets see a real world situation +This can sometimes be confusing so let's see a real world situation. </p> <p> Let's imagine a 3 person situation: John, Mary, and Lisa. John is a good friend of Mary but does not know Lisa; Lisa is a good friend of Mary but does not know John. One day Lisa sends John a signed email. John will fetch -Lisa's Public Key from the keyserver and test the message, if all went ok he +Lisa's Public Key from the keyserver and test the message, if all went ok he will see that whoever wrote that message also created that key. But how do I know it was really the person it claims to be? </p> <p> -He then see's that it is signed by Mary, which he can check because he already +He then sees that it is signed by Mary, which he can check because he already has Mary's key and he trusts that key. With this ring of trust he continues to conclude that the email he received was really written by Lisa. </p> -- [EMAIL PROTECTED] mailing list
