| 1 |
nightmorph 07/07/16 03:00:25 |
| 2 |
|
| 3 |
Modified: gnupg-user.xml |
| 4 |
Log: |
| 5 |
Proper English, grammar, spelling, and some small GuideXML coding style fixes. No content change. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.42 xml/htdocs/doc/en/gnupg-user.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gnupg-user.xml?rev=1.42&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gnupg-user.xml?rev=1.42&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gnupg-user.xml?r1=1.41&r2=1.42 |
| 13 |
|
| 14 |
Index: gnupg-user.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gnupg-user.xml,v |
| 17 |
retrieving revision 1.41 |
| 18 |
retrieving revision 1.42 |
| 19 |
diff -u -r1.41 -r1.42 |
| 20 |
--- gnupg-user.xml 20 Feb 2007 22:07:04 -0000 1.41 |
| 21 |
+++ gnupg-user.xml 16 Jul 2007 03:00:25 -0000 1.42 |
| 22 |
@@ -1,10 +1,11 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
|
| 26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gnupg-user.xml,v 1.41 2007/02/20 22:07:04 nightmorph Exp $ --> |
| 27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gnupg-user.xml,v 1.42 2007/07/16 03:00:25 nightmorph Exp $ --> |
| 28 |
|
| 29 |
<guide link = "/doc/en/gnupg-user.xml"> |
| 30 |
-<title>GnuPG Gentoo user guide</title> |
| 31 |
+<title>GnuPG Gentoo User Guide</title> |
| 32 |
+ |
| 33 |
<author title="Author"> |
| 34 |
<mail link="humpback@g.o">Gustavo Felisberto</mail> |
| 35 |
</author> |
| 36 |
@@ -159,12 +160,12 @@ |
| 37 |
<p> |
| 38 |
Now enter your key passphrase twice. It is a good idea to use a strong password. |
| 39 |
If someone ever gets hold of your private key and cracks your password, they |
| 40 |
-will be able to send messages signed by "you" making everyone believe the mails |
| 41 |
+will be able to send messages signed by "you", making everyone believe the mails |
| 42 |
were sent by you. |
| 43 |
</p> |
| 44 |
|
| 45 |
<p> |
| 46 |
-Then, GnuPG will generate your key. Moving the mouse or having a mp3 playing in |
| 47 |
+Next, GnuPG will generate your key. Moving the mouse or having a mp3 playing in |
| 48 |
the background will help speed up the process because it generates random data. |
| 49 |
</p> |
| 50 |
|
| 51 |
@@ -379,7 +380,7 @@ |
| 52 |
<p> |
| 53 |
You can also send other people's keys that you have signed to the keyserver. We |
| 54 |
could send Luis Pinto's key to the keyserver. This way someone who trusts |
| 55 |
-your key can use the signature that you have placed there to trust Luis' key. |
| 56 |
+your key can use the signature that you have placed there to trust Luis's key. |
| 57 |
</p> |
| 58 |
|
| 59 |
</body> |
| 60 |
@@ -391,7 +392,7 @@ |
| 61 |
<p> |
| 62 |
Now we are going to search for Gustavo Felisberto's key and add it to the |
| 63 |
keyring of John Doe (just in case you did not notice Gustavo Felisberto is the |
| 64 |
-author this guide :) ). |
| 65 |
+author this guide :)). |
| 66 |
</p> |
| 67 |
|
| 68 |
<pre caption="Searching keys from keyservers"> |
| 69 |
@@ -432,10 +433,10 @@ |
| 70 |
<body> |
| 71 |
|
| 72 |
<p> |
| 73 |
-There are cases, when working with certain applications, where you use your GPG |
| 74 |
-key very frequently, which means that you have to type your passphrase a lot of |
| 75 |
+Sometimes working with certain applications requires you to use your GPG key |
| 76 |
+very frequently, which means that you have to type your passphrase a lot of |
| 77 |
times. Several applications used to support a passphrase caching mechanism to |
| 78 |
-make life easier for users, this however disallowed sharing this cache across |
| 79 |
+make life easier for users. However, this disallowed sharing this cache across |
| 80 |
programs (how secure would that be?) and forced applications to reinvent the |
| 81 |
wheel over and over again. |
| 82 |
</p> |
| 83 |
@@ -593,9 +594,9 @@ |
| 84 |
<p> |
| 85 |
Another nice command is <c>gpg --refresh-keys</c>. This will contact the |
| 86 |
keyserver defined in the options file and refresh public keys in your local key |
| 87 |
-ring from there, searching for revoked keys, new id's, new signatures on keys. |
| 88 |
-You should probably run this once or twice a month so that if someone revokes |
| 89 |
-his key you will be notified. |
| 90 |
+ring from there, searching for revoked keys, new IDs, and new signatures on |
| 91 |
+keys. You should probably run this once or twice a month so that if someone |
| 92 |
+revokes his key you will be notified. |
| 93 |
</p> |
| 94 |
|
| 95 |
</body> |
| 96 |
@@ -610,14 +611,14 @@ |
| 97 |
|
| 98 |
<p> |
| 99 |
95% of the time you will use GnuPG with email, signing/encrypting your outgoing |
| 100 |
-messages and reading signed/encrypted messages. So it is only fair that i talk |
| 101 |
+messages and reading signed/encrypted messages. So it is only fair that I talk |
| 102 |
about that first. |
| 103 |
</p> |
| 104 |
|
| 105 |
<p> |
| 106 |
There are two ways two sign/encrypt a email with GnuPG, the old way and the new |
| 107 |
way :). In the old way messages would appear in plain text, with no possible |
| 108 |
-formatting and attached files would be unsigned/unencrypted, here is an example |
| 109 |
+formatting and attached files would be unsigned/unencrypted. Here is an example |
| 110 |
of a message signed the old way: |
| 111 |
</p> |
| 112 |
|
| 113 |
@@ -637,7 +638,7 @@ |
| 114 |
</pre> |
| 115 |
|
| 116 |
<p> |
| 117 |
-Messages this way are no good in todays world, where we have nice GUI's and |
| 118 |
+Messages this way are no good in today's world, where we have nice GUIs and |
| 119 |
email readers that understand html. |
| 120 |
</p> |
| 121 |
|
| 122 |
@@ -645,7 +646,7 @@ |
| 123 |
To solve this an addition to the MIME (Multipurpose Internet Mail Extensions) |
| 124 |
was created. This adds a field to the email that tells the mail reader that the |
| 125 |
full content of the message is signed and/or encrypted. The problem with this |
| 126 |
-is that not all mail readers support this. And some even mess the content, |
| 127 |
+is that not all mail readers support this. And some even mess up the content; |
| 128 |
Microsoft's Outlook is famous for not working with this. |
| 129 |
</p> |
| 130 |
|
| 131 |
@@ -674,7 +675,7 @@ |
| 132 |
<p> |
| 133 |
Now you can see the key managing window. From here we see our good key for John |
| 134 |
Doe. The two trusted keys for Gustavo and Luis, and the untrusted key for Daniel |
| 135 |
-Robbins ( I still have not given him a call to check his fingerprint :) ). |
| 136 |
+Robbins (I still have not given him a call to check his fingerprint :)). |
| 137 |
</p> |
| 138 |
|
| 139 |
</body> |
| 140 |
@@ -772,17 +773,17 @@ |
| 141 |
<p> |
| 142 |
The concept of public key cryptography was originally devised by Whitfield |
| 143 |
Diffie and Martin Hellman in 1976. When I first heard the words "public key" and |
| 144 |
-"cryptography" in the same sentence back in '93 I tought to myself that it would |
| 145 |
-be impossible to do such a thing. In those days there was no Internet (well |
| 146 |
-there was, but not for me) so I went to the public library and asked for books |
| 147 |
-on Cryptography. I must say that I was 16 at the time so the clerk there looked |
| 148 |
-to me in astonishment and brought me a book for children on substitution cyphers |
| 149 |
-(those where you change a letter for another like the famous Caesar Cypher or |
| 150 |
-ROT-13 (Tragbb Ebpxf, naq lbh xabj vg vf tbbq orpnhfr lbh ner ernqvat guvf |
| 151 |
-qbp.), (emerge rotix if you cannot read the preceding text)). I was very upset |
| 152 |
-with this and started to search for more info. It is good to have mathematicians |
| 153 |
-in the family, because as soon as I talked to one of them I was introduced to a |
| 154 |
-new world. |
| 155 |
+"cryptography" in the same sentence back in '93 I thought to myself that it |
| 156 |
+would be impossible to do such a thing. In those days there was no Internet |
| 157 |
+(well there was, but not for me) so I went to the public library and asked for |
| 158 |
+books on Cryptography. I must say that I was 16 at the time so the clerk there |
| 159 |
+looked to me in astonishment and brought me a book for children on substitution |
| 160 |
+cyphers (those where you change a letter for another like the famous Caesar |
| 161 |
+Cypher or ROT-13 (Tragbb Ebpxf, naq lbh xabj vg vf tbbq orpnhfr lbh ner ernqvat |
| 162 |
+guvf qbp.), (<c>emerge rotix</c> if you cannot read the preceding text)). I was |
| 163 |
+very upset with this and started to search for more info. It is good to have |
| 164 |
+mathematicians in the family, because as soon as I talked to one of them I was |
| 165 |
+introduced to a new world. |
| 166 |
</p> |
| 167 |
|
| 168 |
<p> |
| 169 |
@@ -838,12 +839,12 @@ |
| 170 |
protocol. For even more info go to the public library and grab a copy of the |
| 171 |
<uri link="http://www.cacr.math.uwaterloo.ca/hac/">"Handbook of Applied |
| 172 |
Cryptography"</uri> by Alfred J. Menezes, Paul C. van Oorschot and Scott A. |
| 173 |
-Vanstone, also this book is available online for free at the above site. |
| 174 |
+Vanstone. This book is also available online for free at the above site. |
| 175 |
</p> |
| 176 |
|
| 177 |
<p> |
| 178 |
One consequence of the above is that if you cypher a message to me, and you |
| 179 |
-loose the original uncypherd message you will no longer be able to retrieve it |
| 180 |
+loose the original uncyphered message you will no longer be able to retrieve it |
| 181 |
from the cyphered version. |
| 182 |
</p> |
| 183 |
|
| 184 |
@@ -865,14 +866,14 @@ |
| 185 |
when you cypher a message to me you sign it with your private key so that, when |
| 186 |
I receive it, I can first use your public key to check your signature and then |
| 187 |
use my private key to decypher the message. As you can see we could not do |
| 188 |
-that in the setup i described before. |
| 189 |
+that in the setup I described before. |
| 190 |
</p> |
| 191 |
|
| 192 |
<p> |
| 193 |
-Also very important, to sign messages you don't have to cypher them before. So |
| 194 |
-like that you can create messages that can be read by anyone, but that come with |
| 195 |
-your "branding". And if any single character is changed in the message it can |
| 196 |
-(and will) be detected. |
| 197 |
+It's also very important to sign messages so that you don't have to cypher them |
| 198 |
+beforehand. Now you can create messages that can be read by anyone, but that |
| 199 |
+come with your "branding". And if any single character is changed in the message |
| 200 |
+it can (and will) be detected. |
| 201 |
</p> |
| 202 |
|
| 203 |
</body> |
| 204 |
@@ -882,20 +883,20 @@ |
| 205 |
<body> |
| 206 |
|
| 207 |
<p> |
| 208 |
-But lets say that I have no previous contact with you until you send me a |
| 209 |
-message, how do I get your public key, and how do I really know it is yours? |
| 210 |
+But let's say that I have no previous contact with you until you send me a |
| 211 |
+message: how do I get your public key, and how do I really know it is yours? |
| 212 |
</p> |
| 213 |
|
| 214 |
<p> |
| 215 |
To solve this problem public Key Servers were created. When you create your key |
| 216 |
-pair (Public and Private key) you send your public key to the key server. After |
| 217 |
+pair (Public and Private key), you send your public key to the key server. After |
| 218 |
this everyone can retrieve your key from there. This solves the problem of |
| 219 |
finding the key. But how do I really know that that key is the author's key? For |
| 220 |
this another concept must be introduced, and that is key signing: |
| 221 |
</p> |
| 222 |
|
| 223 |
<p> |
| 224 |
-Key signing means that, if I have the public key of another person, and I know |
| 225 |
+Key signing means that if I have the public key of another person, and I know |
| 226 |
<e>for sure</e> that it is really that persons key (it is my personal friend, |
| 227 |
someone I know in real life, etc.) I can sign that public key and send it to |
| 228 |
keyservers, that way I am telling the world: "This key really belongs to the |
| 229 |
@@ -904,20 +905,20 @@ |
| 230 |
</p> |
| 231 |
|
| 232 |
<p> |
| 233 |
-This can sometimes be confusing so lets see a real world situation |
| 234 |
+This can sometimes be confusing so let's see a real world situation. |
| 235 |
</p> |
| 236 |
|
| 237 |
<p> |
| 238 |
Let's imagine a 3 person situation: John, Mary, and Lisa. John is a good |
| 239 |
friend of Mary but does not know Lisa; Lisa is a good friend of Mary but |
| 240 |
does not know John. One day Lisa sends John a signed email. John will fetch |
| 241 |
-Lisa's Public Key from the keyserver and test the message, if all went ok he |
| 242 |
+Lisa's Public Key from the keyserver and test the message, if all went ok he |
| 243 |
will see that whoever wrote that message also created that key. But how do I |
| 244 |
know it was really the person it claims to be? |
| 245 |
</p> |
| 246 |
|
| 247 |
<p> |
| 248 |
-He then see's that it is signed by Mary, which he can check because he already |
| 249 |
+He then sees that it is signed by Mary, which he can check because he already |
| 250 |
has Mary's key and he trusts that key. With this ring of trust he continues to |
| 251 |
conclude that the email he received was really written by Lisa. |
| 252 |
</p> |
| 253 |
|
| 254 |
|
| 255 |
|
| 256 |
-- |
| 257 |
gentoo-doc-cvs@g.o mailing list |
Archives