Commit | Line | Data |
---|---|---|
bdf319c4 | 1 | <!DOCTYPE html> |
c35c9b77 | 2 | <html lang="en"> |
116f80c3 | 3 | <head> |
39c89f44 TG |
4 | <meta http-equiv="content-type" content="text/html; charset=utf-8" /> |
5 | <title>Email Self-Defense - a guide to fighting surveillance with GnuPG | |
6 | encryption</title> | |
7 | <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, | |
8 | email, Enigmail" /> | |
9 | <meta name="description" content="Email surveillance violates our fundamental | |
10 | rights and makes free speech risky. This guide will teach you email | |
70f3b176 | 11 | self-defense in 40 minutes with GnuPG." /> |
39c89f44 TG |
12 | <meta name="viewport" content="width=device-width, initial-scale=1" /> |
13 | <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" /> | |
14 | <link rel="shortcut icon" | |
15 | href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" /> | |
116f80c3 | 16 | </head> |
39c89f44 | 17 | |
5a396903 | 18 | <body><iframe src="//static.fsf.org/nosvn/banners/2017fundraiser/" width="100%" height="100%" scrolling="no" style="overflow: hidden; border: 0 none; display: block;"></iframe> |
b3eff1c4 | 19 | |
39c89f44 TG |
20 | <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ --> |
21 | <header class="row" id="header"><div> | |
116f80c3 | 22 | |
39c89f44 | 23 | <h1>Email Self-Defense</h1> |
116f80c3 | 24 | |
39c89f44 TG |
25 | <!-- Language list for browsers that do not have JS enabled --> |
26 | <ul id="languages" class="os"> | |
e897555f | 27 | <li><a class="current" href="/en">English - v4.0</a></li> |
f3befb3a | 28 | <li><a href="/ar">العربية <span class="tip">tip</span></a></li> |
e897555f TG |
29 | <li><a href="/cs">Čeština - v4.0</a></li> |
30 | <li><a href="/de">Deutsch - v3.0</a></li> | |
31 | <li><a href="/el">ελληνικά - v3.0</a></li> | |
32 | <li><a href="/es">español - v4.0</a></li> | |
33 | <li><a href="/fa">فارسی - v4.0</a></li> | |
34 | <li><a href="/fr">français - v4.0</a></li> | |
35 | <li><a href="/it">italiano - v3.0</a></li> | |
36 | <li><a href="/ja">日本語 - v4.0</a></li> | |
f3befb3a TG |
37 | <li><a href="/ko">한국어 <span class="tip">tip</span></a></li> |
38 | <li><a href="/ml">മലയാളം <span class="tip">tip</span></a></li> | |
e897555f TG |
39 | <li><a href="/pt-br">português do Brasil - v3.0</a></li> |
40 | <li><a href="/ro">română - v3.0</a></li> | |
41 | <li><a href="/ru">русский - v4.0</a></li> | |
5163d881 | 42 | <li><a href="/sq">Shqip - v4.0</a></li> |
e897555f TG |
43 | <li><a href="/sv">svenska - v4.0</a></li> |
44 | <li><a href="/tr">Türkçe - v4.0</a></li> | |
f3befb3a TG |
45 | <li><a href="/zh-hans">简体中文 <span class="tip">tip</span></a></li> |
46 | <li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span | |
39c89f44 TG |
47 | style="color: #2F5FAA;">Translate!</span></strong></a></li> |
48 | </ul> | |
49 | ||
50 | <ul id="menu" class="os"> | |
51 | <li class="spacer"><a href="index.html" class="current">GNU/Linux</a></li> | |
52 | <li><a href="mac.html">Mac OS</a></li> | |
53 | <li><a href="windows.html">Windows</a></li> | |
54 | <li><a href="workshops.html">Teach your friends</a></li> | |
55 | <li><a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email | |
56 | encryption for everyone via %40fsf">Share | |
57 | <img | |
58 | src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" | |
59 | class="share-logo" | |
60 | alt="[GNU Social]" /> | |
61 | <img | |
62 | src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png" | |
63 | class="share-logo" | |
64 | alt="[Pump.io]" /> | |
65 | <img | |
66 | src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" | |
67 | class="share-logo" | |
68 | alt="[Reddit]" /> | |
69 | <img | |
70 | src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" | |
71 | class="share-logo" | |
72 | alt="[Hacker News]" /> | |
73 | </a></li> | |
74 | </ul> | |
75 | ||
76 | <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ --> | |
77 | <div id="fsf-intro"> | |
78 | ||
79 | <h3><a href="http://u.fsf.org/ys"><img | |
80 | alt="Free Software Foundation" | |
81 | src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" /> | |
82 | </a></h3> | |
83 | ||
84 | <div class="fsf-emphasis"> | |
85 | ||
86 | <p>We fight for computer users' rights, and promote the development of free (as | |
87 | in freedom) software. Resisting bulk surveillance is very important to us.</p> | |
88 | ||
89 | <p><strong>Please donate to support Email Self-Defense. We need to keep | |
90 | improving it, and making more materials, for the benefit of people around | |
91 | the world taking the first step towards protecting their privacy.</strong></p> | |
92 | ||
93 | </div> | |
94 | ||
95 | <p><a | |
96 | href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img | |
97 | alt="Donate" | |
98 | src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a></p> | |
99 | ||
100 | </div><!-- End #fsf-intro --> | |
101 | ||
102 | <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ --> | |
103 | <div class="intro"> | |
104 | ||
105 | <p><a id="infographic" href="infographic.html"><img | |
106 | src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" | |
107 | alt="View & share our infographic →" /></a> | |
108 | Bulk surveillance violates our fundamental rights and makes free speech | |
109 | risky. This guide will teach you a basic surveillance self-defense skill: | |
110 | email encryption. Once you've finished, you'll be able to send and receive | |
111 | emails that are scrambled to make sure anyone, including a surveillance agent | |
112 | or thief, intercepting your email can't read them. All you need is a computer | |
113 | with an Internet connection, an email account, and about forty minutes.</p> | |
114 | ||
115 | <p>Even if you have nothing to hide, using encryption helps protect the privacy | |
116 | of people you communicate with, and makes life difficult for bulk surveillance | |
117 | systems. If you do have something important to hide, you're in good company; | |
118 | these are the same tools that whistleblowers use to protect their identities | |
119 | while shining light on human rights abuses, corruption and other crimes.</p> | |
120 | ||
121 | <p>In addition to using encryption, standing up | |
122 | to surveillance requires fighting politically for a <a | |
123 | href="http://gnu.org/philosophy/surveillance-vs-democracy.html">reduction | |
124 | in the amount of data collected on us</a>, but the essential first step is | |
125 | to protect yourself and make surveillance of your communication as difficult | |
126 | as possible. This guide helps you do that. It is designed for beginners, but | |
127 | if you already know the basics of GnuPG or are an experienced free software | |
128 | user, you'll enjoy the advanced tips and the <a href="workshops.html">guide | |
129 | to teaching your friends</a>.</p> | |
130 | ||
131 | </div><!-- End .intro --> | |
132 | </div></header><!-- End #header --> | |
133 | ||
134 | <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ --> | |
135 | <section class="row" id="section1"><div> | |
136 | ||
137 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
138 | <div class="section-intro"> | |
139 | ||
140 | <h2><em>#1</em> Get the pieces</h2> | |
141 | ||
142 | <p class="notes">This guide relies on software which is <a | |
143 | href="https://www.gnu.org/philosophy/free-sw.html">freely licensed</a>; | |
144 | it's completely transparent and anyone can copy it or make their | |
145 | own version. This makes it safer from surveillance than proprietary | |
146 | software (like Windows). Learn more about free software at <a | |
147 | href="https://u.fsf.org/ys">fsf.org</a>.</p> | |
148 | ||
149 | <p>Most GNU/Linux operating systems come with GnuPG installed on them, | |
150 | so you don't have to download it. Before configuring GnuPG though, you'll | |
151 | need the IceDove desktop email program installed on your computer. Most | |
152 | GNU/Linux distributions have IceDove installed already, though it may be | |
153 | under the alternate name "Thunderbird." Email programs are another way to | |
154 | access the same email accounts you can access in a browser (like Gmail), | |
155 | but provide extra features.</p> | |
156 | ||
157 | <p>If you already have an email program, you can skip to <a | |
158 | href="#step-1b">Step 1.b</a>.</p> | |
159 | ||
160 | </div><!-- End .section-intro --> | |
161 | ||
162 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
163 | <div id="step-1a" class="step"> | |
164 | <div class="sidebar"> | |
165 | ||
166 | <p><img | |
167 | src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" | |
168 | alt="Step 1.A: Install Wizard" /></p> | |
169 | ||
170 | </div><!-- /.sidebar --> | |
171 | <div class="main"> | |
172 | ||
173 | <h3><em>Step 1.a</em> Set up your email program with your email account</h3> | |
174 | ||
175 | <p>Open your email program and follow the wizard (step-by-step walkthrough) | |
176 | that sets it up with your email account.</p> | |
177 | ||
178 | <p>Look for the letters SSL, TLS, or STARTTLS to the right of the servers | |
179 | when you're setting up your account. If you don't see them, you will still | |
180 | be able to use encryption, but this means that the people running your email | |
181 | system are running behind the industry standard in protecting your security | |
182 | and privacy. We recommend that you send them a friendly email asking them | |
183 | to enable SSL, TLS, or STARTTLS for your email server. They will know what | |
184 | you're talking about, so it's worth making the request even if you aren't | |
185 | an expert on these security systems.</p> | |
186 | ||
187 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
188 | <div class="troubleshooting"> | |
189 | ||
190 | <h4>Troubleshooting</h4> | |
191 | ||
192 | <dl> | |
193 | <dt>The wizard doesn't launch</dt> | |
194 | <dd>You can launch the wizard yourself, but the menu option for doing so is | |
195 | named differently in each email program. The button to launch it will be in | |
196 | the program's main menu, under "New" or something similar, titled something | |
197 | like "Add account" or "New/Existing email account."</dd> | |
198 | ||
199 | <dt>The wizard can't find my account or isn't downloading my mail</dt> | |
200 | <dd>Before searching the Web, we recommend you start by asking other people | |
201 | who use your email system, to figure out the correct settings.</dd> | |
202 | ||
203 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
204 | <dd class="feedback">Please let us know on the <a | |
205 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback | |
206 | page</a>.</dd> | |
207 | </dl> | |
208 | ||
209 | </div><!-- /.troubleshooting --> | |
210 | </div><!-- End .main --> | |
211 | </div><!-- End #step1-a .step --> | |
212 | ||
213 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
214 | <div id="step-1b" class="step"> | |
215 | <div class="sidebar"> | |
216 | ||
217 | <ul class="images"> | |
218 | <li><img | |
219 | src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png" | |
220 | alt="Step 1.B: Tools -> Add-ons" /></li> | |
221 | <li><img | |
222 | src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png" | |
223 | alt="Step 1.B: Search Add-ons" /></li> | |
224 | <li><img | |
225 | src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png" | |
226 | alt="Step 1.B: Install Add-ons" /></li> | |
227 | </ul> | |
228 | ||
229 | </div><!-- /.sidebar --> | |
230 | <div class="main"> | |
231 | ||
232 | <h3><em>Step 1.b</em> Install the Enigmail plugin for your email program</h3> | |
233 | ||
234 | <p>In your email program's menu, select Add-ons (it may be in the Tools | |
235 | section). Make sure Extensions is selected on the left. Do you see Enigmail? If | |
236 | so, skip this step.</p> | |
237 | ||
238 | <p>If not, search "Enigmail" with the search bar in the upper right. You | |
239 | can take it from here. Restart your email program when you're done.</p> | |
240 | ||
241 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
242 | <div class="troubleshooting"> | |
243 | ||
244 | <h4>Troubleshooting</h4> | |
245 | ||
246 | <dl> | |
247 | <dt>I can't find the menu.</dt> | |
248 | <dd>In many new email programs, the main menu is represented by an image of | |
249 | three stacked horizontal bars.</dd> | |
250 | ||
251 | <dt>My email looks weird</dt> | |
252 | <dd>Enigmail doesn't tend to play nice with HTML, which is used to format | |
253 | emails, so it may disable your HTML formatting automatically. To send an | |
254 | HTML-formatted email without encryption or a signature, hold down the Shift | |
255 | key when you select compose. You can then write an email as if Enigmail | |
256 | wasn't there.</dd> | |
257 | ||
258 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
259 | <dd class="feedback">Please let us know on the <a | |
260 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback | |
261 | page</a>.</dd> | |
262 | </dl> | |
263 | ||
264 | </div><!-- /.troubleshooting --> | |
265 | </div><!-- End .main --> | |
266 | </div><!-- End #step-1b .step --> | |
267 | </div></section><!-- End #section1 --> | |
268 | ||
269 | <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ --> | |
270 | <section class="row" id="section2"><div> | |
271 | ||
272 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
273 | <div class="section-intro"> | |
274 | ||
275 | <h2><em>#2</em> Make your keys</h2> | |
276 | ||
277 | <p>To use the GnuPG system, you'll need a public key and a private key (known | |
278 | together as a keypair). Each is a long string of randomly generated numbers | |
279 | and letters that are unique to you. Your public and private keys are linked | |
280 | together by a special mathematical function.</p> | |
281 | ||
282 | <p>Your public key isn't like a physical key, because it's stored in the open | |
283 | in an online directory called a keyserver. People download it and use it, | |
284 | along with GnuPG, to encrypt emails they send to you. You can think of the | |
285 | keyserver as a phonebook; people who want to send you encrypted email can | |
286 | look up your public key.</p> | |
287 | ||
288 | <p>Your private key is more like a physical key, because you keep it to | |
289 | yourself (on your computer). You use GnuPG and your private key together to | |
290 | descramble encrypted emails other people send to you. <span style="font-weight: | |
291 | bold;">You should never share you private key with anyone, under any | |
292 | circumstances.</span></p> | |
293 | ||
294 | <p>In addition to encryption and decryption, you can also use these keys to | |
295 | sign messages and check the authenticity of other people's signatures. We'll | |
296 | discuss this more in the next section.</p> | |
297 | ||
298 | </div><!-- End .section-intro --> | |
299 | ||
300 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
301 | <div id="step-2a" class="step"> | |
302 | <div class="sidebar"> | |
303 | ||
304 | <p><img | |
305 | src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" | |
306 | alt="Step 2.A: Make a Keypair" /></p> | |
307 | ||
308 | </div><!-- /.sidebar --> | |
309 | <div class="main"> | |
310 | ||
311 | <h3><em>Step 2.a</em> Make a keypair</h3> | |
312 | ||
313 | <p>The Enigmail Setup wizard may start automatically. If it doesn't, select | |
314 | Enigmail → Setup Wizard from your email program's menu. You don't need | |
315 | to read the text in the window that pops up unless you'd like to, but it's | |
316 | good to read the text on the later screens of the wizard. Click Next with | |
317 | the default options selected, except in these instances, which are listed | |
318 | in the order they appear:</p> | |
319 | ||
320 | <ul> | |
321 | <li>On the screen titled "Encryption," select "Encrypt all of my messages | |
322 | by default, because privacy is critical to me."</li> | |
323 | ||
324 | <li>On the screen titled "Signing," select "Don't sign my messages by | |
325 | default."</li> | |
326 | ||
327 | <li>On the screen titled "Key Selection," select "I want to create a new | |
328 | key pair for signing and encrypting my email."</li> | |
329 | ||
330 | <li>On the screen titled "Create Key," pick a strong password! You can | |
331 | do it manually, or you can use the Diceware method. Doing it manually | |
332 | is faster but not as secure. Using Diceware takes longer and requires | |
333 | dice, but creates a password that is much harder for attackers figure | |
334 | out. To use it, read the section "Make a secure passphrase with Diceware" in <a | |
335 | href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">this | |
336 | article</a> by Micah Lee.</li> | |
337 | </ul> | |
338 | ||
339 | <p>If you'd like to pick a password manually, come up with something | |
340 | you can remember which is at least twelve characters long, and includes | |
341 | at least one lower case and upper case letter and at least one number or | |
342 | punctuation symbol. Never pick a password you've used elsewhere. Don't use | |
343 | any recognizable patterns, such as birthdays, telephone numbers, pets' names, | |
344 | song lyrics, quotes from books, and so on.</p> | |
345 | ||
346 | <p class="notes">The program will take a little while to finish the next | |
347 | step, the "Key Creation" screen. While you wait, do something else with your | |
348 | computer, like watching a movie or browsing the Web. The more you use the | |
349 | computer at this point, the faster the key creation will go.</p> | |
350 | ||
351 | <p><span style="font-weight: bold;">When the "Key Generation Completed" screen | |
352 | pops up, select Generate Certificate and choose to save it in a safe place on | |
353 | your computer (we recommend making a folder called "Revocation Certificate" | |
354 | in your home folder and keeping it there). This step is essential for your | |
355 | email self-defense, as you'll learn more about in <a href="#section5">Section | |
356 | 5</a>.</span></p> | |
357 | ||
358 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
359 | <div class="troubleshooting"> | |
360 | ||
361 | <h4>Troubleshooting</h4> | |
362 | ||
363 | <dl> | |
364 | <dt>I can't find the Enigmail menu.</dt> | |
365 | <dd>In many new email programs, the main menu is represented by an image | |
366 | of three stacked horizontal bars. Enigmail may be inside a section called | |
367 | Tools.</dd> | |
368 | ||
369 | <dt>The wizard says that it cannot find GnuPG.</dt> | |
370 | <dd>Open whatever program you usually use for installing software, and search | |
371 | for GnuPG, then install it. Then restart the Enigmail setup wizard by going | |
372 | to Enigmail → Setup Wizard.</dd> | |
373 | ||
374 | <dt>My email looks weird</dt> | |
375 | <dd>Enigmail doesn't tend to play nice with HTML, which is used to format | |
376 | emails, so it may disable your HTML formatting automatically. To send an | |
377 | HTML-formatted email without encryption or a signature, hold down the Shift | |
378 | key when you select compose. You can then write an email as if Enigmail | |
379 | wasn't there.</dd> | |
380 | ||
381 | <dt>More resources</dt> | |
382 | <dd>If you're having trouble with our | |
383 | instructions or just want to learn more, check out <a | |
384 | href="https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">Enigmail's | |
385 | wiki instructions for key generation</a>.</dd> | |
386 | ||
387 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
388 | <dd class="feedback">Please let us know on the <a | |
389 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback | |
390 | page</a>.</dd> | |
391 | </dl> | |
392 | ||
393 | </div><!-- /.troubleshooting --> | |
394 | ||
395 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
396 | <div class="troubleshooting"> | |
397 | ||
398 | <h4>Advanced</h4> | |
399 | ||
400 | <dl> | |
401 | <dt>Command line key generation</dt> | |
402 | <dd>If you prefer using the command line for a higher | |
403 | degree of control, you can follow the documentation from <a | |
404 | href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy | |
405 | Handbook</a>. Make sure you stick with "RSA and RSA" (the default), | |
406 | because it's newer and more secure than the algorithms the documentation | |
407 | recommends. Also make sure your key is at least 2048 bits, or 4096 if you | |
408 | want to be extra secure.</dd> | |
409 | ||
410 | <dt>Advanced key pairs</dt> | |
411 | <dd>When GnuPG creates a new keypair, it compartmentalizes | |
412 | the encryption function from the signing function through <a | |
413 | href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use | |
414 | subkeys carefully, you can keep your GnuPG identity much more | |
415 | secure and recover from a compromised key much more quickly. <a | |
416 | href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a> | |
417 | and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a> | |
418 | provide good guides for setting up a secure subkey configuration.</dd> | |
419 | </dl> | |
420 | ||
421 | </div><!-- /.troubleshooting --> | |
422 | </div><!-- End .main --> | |
423 | </div><!-- End #step-2a .step --> | |
424 | ||
425 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
426 | <div id="step-2b" class="step"> | |
427 | <div class="main"> | |
428 | ||
429 | <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3> | |
430 | ||
431 | <p>In your email program's menu, select Enigmail → Key Management.</p> | |
432 | ||
433 | <p>Right click on your key and select Upload Public Keys to Keyserver. Use | |
434 | the default keyserver in the popup.</p> | |
435 | ||
436 | <p class="notes">Now someone who wants to send you an encrypted message can | |
437 | download your public key from the Internet. There are multiple keyservers | |
438 | that you can select from the menu when you upload, but they are all copies | |
439 | of each other, so it doesn't matter which one you use. However, it sometimes | |
440 | takes a few hours for them to match each other when a new key is uploaded.</p> | |
441 | ||
442 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
443 | <div class="troubleshooting"> | |
444 | ||
445 | <h4>Troubleshooting</h4> | |
446 | ||
447 | <dl> | |
448 | <dt>The progress bar never finishes</dt> | |
449 | <dd>Close the upload popup, make sure you are connected to the Internet, | |
450 | and try again. If that doesn't work, try again, selecting a different | |
451 | keyserver.</dd> | |
452 | ||
453 | <dt>My key doesn't appear in the list</dt> | |
454 | <dd>Try checking "Display All Keys by Default."</dd> | |
455 | ||
456 | <dt>More documentation</dt> | |
457 | <dd>If you're having trouble with our | |
458 | instructions or just want to learn more, check out <a | |
459 | href="https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">Enigmail's | |
460 | documentation</a>.</dd> | |
461 | ||
462 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
463 | <dd class="feedback">Please let us know on the <a | |
464 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback | |
465 | page</a>.</dd> | |
466 | </dl> | |
467 | ||
468 | </div><!-- /.troubleshooting --> | |
469 | ||
470 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
471 | <div class="troubleshooting"> | |
472 | ||
473 | <h4>Advanced</h4> | |
474 | ||
475 | <dl> | |
476 | <dt>Uploading a key from the command line</dt> | |
477 | <dd>You can also upload your keys to a keyserver through the <a | |
478 | href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a | |
479 | href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a> | |
480 | maintains a list of highly interconnected keyservers. You can also <a | |
481 | href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export | |
482 | your key</a> as a file on your computer.</dd> | |
483 | </dl> | |
484 | ||
485 | </div><!-- /.troubleshooting --> | |
486 | </div><!-- End .main --> | |
487 | </div><!-- End #step-2b .step --> | |
488 | ||
489 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
490 | <div id="terminology" class="step"> | |
491 | <div class="main"> | |
492 | ||
493 | <h3>GnuPG, OpenPGP, what?</h3> | |
494 | ||
495 | <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP | |
496 | are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the | |
497 | encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG) | |
498 | is the program that implements the standard. Enigmail is a plug-in program | |
499 | for your email program that provides an interface for GnuPG.</p> | |
500 | ||
501 | </div><!-- End .main --> | |
502 | </div><!-- End #terminology.step--> | |
503 | </div></section><!-- End #section2 --> | |
504 | ||
505 | <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ --> | |
506 | <section class="row" id="section3"><div> | |
507 | ||
508 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
509 | <div class="section-intro"> | |
510 | ||
511 | <h2><em>#3</em> Try it out!</h2> | |
512 | ||
513 | <p>Now you'll try a test correspondence with a computer program named Edward, | |
514 | who knows how to use encryption. Except where noted, these are the same | |
515 | steps you'd follow when corresponding with a real, live person.</p> | |
516 | ||
517 | <!-- <p>NOTE: Edward is currently having some technical difficulties, so he | |
518 | may take a long time to respond, or not respond at all. We're sorry about | |
519 | this and we're working hard to fix it. Your key will still work even without | |
520 | testing with Edward.</p> --> | |
521 | </div><!-- End .section-intro --> | |
522 | ||
523 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
524 | <div id="step-3a" class="step"> | |
525 | <div class="sidebar"> | |
526 | ||
527 | <p><img | |
528 | src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" | |
529 | alt="Try it out." /></p> | |
530 | ||
531 | </div><!-- /.sidebar --> | |
532 | <div class="main"> | |
533 | ||
534 | <h3><em>Step 3.a</em> Send Edward your public key</h3> | |
535 | ||
536 | <p>This is a special step that you won't have to do when corresponding | |
537 | with real people. In your email program's menu, go to Enigmail → Key | |
538 | Management. You should see your key in the list that pops up. Right click | |
539 | on your key and select Send Public Keys by Email. This will create a new | |
540 | draft message, as if you had just hit the Write button.</p> | |
541 | ||
542 | <p>Address the message to <a | |
543 | href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word | |
544 | (whatever you want) in the subject and body of the email. Don't send yet.</p> | |
545 | ||
546 | <p>The lock icon in the top left should be yellow, meaning encryption is | |
547 | turned on. We want this first special message to be unencrypted, so | |
548 | click the icon once to turn it off. The lock should become grey, with a | |
549 | blue dot on it (to alert you that the setting has been changed from the | |
550 | default). Once encryption is off, hit Send.</p> | |
551 | ||
552 | <p class="notes">It may take two or three minutes for Edward to | |
553 | respond. In the meantime, you might want to skip ahead and check out the <a | |
554 | href="#section5">Use it Well</a> section of this guide. Once he's responded, | |
555 | head to the next step. From here on, you'll be doing just the same thing as | |
556 | when corresponding with a real person.</p> | |
557 | ||
558 | <p>When you open Edward's reply, GnuPG may prompt you for your password | |
559 | before using your private key to decrypt it.</p> | |
560 | ||
561 | </div><!-- End .main --> | |
562 | </div><!-- End #step-3a .step --> | |
563 | ||
564 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
565 | <div id="step-3b" class="step"> | |
566 | <div class="main"> | |
567 | ||
568 | <h3><em>Step 3.b</em> Send a test encrypted email</h3> | |
569 | ||
570 | <p>Write a new email in your email program, addressed to <a | |
571 | href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject | |
572 | "Encryption test" or something similar and write something in the body.</p> | |
573 | ||
574 | <p>The lock icon in the top left of the window should be yellow, meaning | |
575 | encryption is on. This will be your default from now on.</p> | |
576 | ||
577 | <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll | |
578 | get to this in a moment.</p> | |
579 | ||
580 | <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, | |
581 | not trusted or not found."</p> | |
582 | ||
583 | <p>To encrypt an email to Edward, you need his public key, so now you'll have | |
584 | Enigmail download it from a keyserver. Click Download Missing Keys and use | |
585 | the default in the pop-up that asks you to choose a keyserver. Once it finds | |
586 | keys, check the first one (Key ID starting with C), then select ok. Select | |
587 | ok in the next pop-up.</p> | |
588 | ||
589 | <p>Now you are back at the "Recipients not valid, not trusted or not found" | |
590 | screen. Check the box in front of Edward's key and click Send.</p> | |
591 | ||
592 | <p class="notes">Since you encrypted this email with Edward's public key, | |
593 | Edward's private key is required to decrypt it. Edward is the only one with | |
594 | his private key, so no one except him can decrypt it.</p> | |
595 | ||
596 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
597 | <div class="troubleshooting"> | |
598 | ||
599 | <h4>Troubleshooting</h4> | |
600 | ||
601 | <dl> | |
602 | <dt>Enigmail can't find Edward's key</dt> | |
603 | <dd>Close the pop-ups that have appeared since you clicked Send. Make sure | |
604 | you are connected to the Internet and try again. If that doesn't work, repeat | |
605 | the process, choosing a different keyserver when it asks you to pick one.</dd> | |
606 | ||
607 | <dt>Unscrambled messages in the Sent folder</dt> | |
608 | <dd>Even though you can't decrypt messages encrypted to someone else's key, | |
609 | your email program will automatically save a copy encrypted to your public key, | |
610 | which you'll be able to view from the Sent folder like a normal email. This | |
611 | is normal, and it doesn't mean that your email was not sent encrypted.</dd> | |
612 | ||
613 | <dt>More resources</dt> | |
614 | <dd>If you're still having trouble with our | |
615 | instructions or just want to learn more, check out <a | |
616 | href="https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">Enigmail's | |
617 | wiki</a>.</dd> | |
618 | ||
619 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
620 | <dd class="feedback">Please let us know on the <a | |
621 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback | |
622 | page</a>.</dd> | |
623 | </dl> | |
624 | ||
625 | </div><!-- /.troubleshooting --> | |
626 | ||
627 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
628 | <div class="troubleshooting"> | |
629 | ||
630 | <h4>Advanced</h4> | |
631 | ||
632 | <dl> | |
633 | <dt>Encrypt messages from the command line</dt> | |
634 | <dd>You can also encrypt and decrypt messages and files from the <a | |
635 | href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>, | |
636 | if that's your preference. The option --armor makes the encrypted output | |
637 | appear in the regular character set.</dd> | |
638 | </dl> | |
639 | ||
640 | </div><!-- /.troubleshooting --> | |
641 | </div><!-- End .main --> | |
642 | </div><!-- End #step-3b .step --> | |
643 | ||
644 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
645 | <div id="step-headers_unencrypted" class="step"> | |
646 | <div class="main"> | |
647 | ||
648 | <h3><em>Important:</em> Security tips</h3> | |
19e80165 | 649 | |
39c89f44 TG |
650 | <p>Even if you encrypt your email, the subject line is not encrypted, so |
651 | don't put private information there. The sending and receiving addresses | |
652 | aren't encrypted either, so a surveillance system can still figure out who | |
653 | you're communicating with. Also, surveillance agents will know that you're | |
654 | using GnuPG, even if they can't figure out what you're saying. When you | |
655 | send attachments, Enigmail will give you the choice to encrypt them or not, | |
656 | independent of the actual email.</p> | |
bdf319c4 | 657 | |
39c89f44 TG |
658 | </div><!-- End .main --> |
659 | </div><!-- End #step-headers_unencrypted .step--> | |
d85363e7 | 660 | |
39c89f44 TG |
661 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> |
662 | <div id="step-3c" class="step"> | |
663 | <div class="main"> | |
664 | ||
665 | <h3><em>Step 3.c</em> Receive a response</h3> | |
666 | ||
667 | <p>When Edward receives your email, he will use his private key to decrypt | |
668 | it, then use your public key (which you sent him in <a href="#step-3a">Step | |
669 | 3.A</a>) to encrypt his reply to you.</p> | |
670 | ||
671 | <p class="notes">It may take two or three minutes for Edward to | |
672 | respond. In the meantime, you might want to skip ahead and check out the <a | |
673 | href="#section5">Use it Well</a> section of this guide.</p> | |
674 | ||
675 | <p>When you receive Edward's email and open it, Enigmail will automatically | |
676 | detect that it is encrypted with your public key, and then it will use your | |
677 | private key to decrypt it.</p> | |
678 | ||
679 | <p>Notice the bar that Enigmail shows you above the message, with information | |
680 | about the status of Edward's key.</p> | |
681 | ||
682 | </div><!-- End .main --> | |
683 | </div><!-- End #step-3c .step --> | |
684 | ||
685 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
686 | <div id="step-3d" class="step"> | |
687 | <div class="main"> | |
688 | ||
689 | <h3><em>Step 3.d</em> Send a test signed email</h3> | |
690 | ||
691 | <p>GnuPG includes a way for you to sign messages and files, verifying that | |
692 | they came from you and that they weren't tampered with along the way. These | |
693 | signatures are stronger than their pen-and-paper cousins -- they're impossible | |
694 | to forge, because they're impossible to create without your private key | |
695 | (another reason to keep your private key safe).</p> | |
696 | ||
697 | <p>You can sign messages to anyone, so it's a great way to make people | |
698 | aware that you use GnuPG and that they can communicate with you securely. If | |
699 | they don't have GnuPG, they will be able to read your message and see your | |
700 | signature. If they do have GnuPG, they'll also be able to verify that your | |
701 | signature is authentic.</p> | |
702 | ||
703 | <p>To sign an email to Edward, compose any message to him and click the | |
704 | pencil icon next to the lock icon so that it turns gold. If you sign a | |
705 | message, GnuPG may ask you for your password before it sends the message, | |
706 | because it needs to unlock your private key for signing.</p> | |
707 | ||
708 | <p>With the lock and pencil icons, you can choose whether each message will | |
709 | be encrypted, signed, both, or neither.</p> | |
710 | ||
711 | </div> | |
712 | </div> | |
713 | ||
714 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
715 | <div id="step-3e" class="step"> | |
716 | <div class="main"> | |
717 | ||
718 | <h3><em>Step 3.e</em> Receive a response</h3> | |
719 | ||
720 | <p>When Edward receives your email, he will use your public key (which you | |
721 | sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature | |
722 | is authentic and the message you sent has not been tampered with.</p> | |
723 | ||
724 | <p class="notes">It may take two or three minutes for Edward to | |
725 | respond. In the meantime, you might want to skip ahead and check out the <a | |
726 | href="#section5">Use it Well</a> section of this guide.</p> | |
727 | ||
728 | <p>Edward's reply will arrive encrypted, because he prefers to use encryption | |
729 | whenever possible. If everything goes according to plan, it should say | |
730 | "Your signature was verified." If your test signed email was also encrypted, | |
731 | he will mention that first.</p> | |
732 | ||
733 | </div><!-- End .main --> | |
734 | </div><!-- End #step-3e .step --> | |
735 | </div></section> | |
736 | ||
737 | <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ --> | |
738 | <section class="row" id="section4"><div> | |
739 | ||
740 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
741 | <div class="section-intro"> | |
742 | ||
743 | <h2><em>#4</em> Learn the Web of Trust</h2> | |
744 | ||
745 | <p>Email encryption is a powerful technology, but it has a weakness; | |
746 | it requires a way to verify that a person's public key is actually | |
747 | theirs. Otherwise, there would be no way to stop an attacker from making | |
748 | an email address with your friend's name, creating keys to go with it and | |
749 | impersonating your friend. That's why the free software programmers that | |
750 | developed email encryption created keysigning and the Web of Trust.</p> | |
751 | ||
752 | <p>When you sign someone's key, you are publicly saying that you've verified | |
753 | that it belongs to them and not someone else.</p> | |
754 | ||
755 | <p>Signing keys and signing messages use the same type of mathematical | |
756 | operation, but they carry very different implications. It's a good practice | |
757 | to generally sign your email, but if you casually sign people's keys, you | |
758 | may accidently end up vouching for the identity of an imposter.</p> | |
759 | ||
760 | <p>People who use your public key can see who has signed it. Once you've | |
761 | used GnuPG for a long time, your key may have hundreds of signatures. You | |
762 | can consider a key to be more trustworthy if it has many signatures from | |
763 | people that you trust. The Web of Trust is a constellation of GnuPG users, | |
764 | connected to each other by chains of trust expressed through signatures.</p> | |
765 | ||
766 | </div><!-- End .section-intro --> | |
767 | ||
768 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
769 | <div id="step-4a" class="step"> | |
770 | <div class="sidebar"> | |
771 | ||
772 | <p><img | |
773 | src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" | |
774 | alt="Section 4: Web of Trust" /></p> | |
775 | ||
776 | </div><!-- /.sidebar --> | |
777 | <div class="main"> | |
778 | ||
779 | <h3><em>Step 4.a</em> Sign a key</h3> | |
780 | ||
781 | <p>In your email program's menu, go to Enigmail → Key Management.</p> | |
782 | ||
783 | <p>Right click on Edward's public key and select Sign Key from the context | |
784 | menu.</p> | |
785 | ||
786 | <p>In the window that pops up, select "I will not answer" and click ok.</p> | |
787 | ||
788 | <p>Now you should be back at the Key Management menu. Select Keyserver → | |
789 | Upload Public Keys and hit ok.</p> | |
790 | ||
791 | <p class="notes">You've just effectively said "I trust that Edward's public | |
792 | key actually belongs to Edward." This doesn't mean much because Edward isn't | |
793 | a real person, but it's good practice.</p> | |
794 | ||
795 | <!--<div id="pgp-pathfinder"> | |
796 | ||
797 | <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" | |
798 | method="get"> | |
799 | ||
800 | <p><strong>From:</strong><input type="text" placeholder="xD41A008" | |
801 | name="FROM"></p> | |
802 | ||
803 | <p><strong>To:</strong><input type="text" placeholder="50BD01x4" name="TO"></p> | |
804 | ||
805 | <p class="buttons"><input type="submit" value="trust paths" name="PATHS"><input | |
806 | type="reset" value="reset" name=".reset"></p> | |
807 | ||
808 | </form> | |
809 | ||
810 | </div>End #pgp-pathfinder --> | |
811 | </div><!-- End .main --> | |
812 | </div><!-- End #step-4a .step --> | |
813 | ||
814 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
815 | <div id="step-identify_keys" class="step"> | |
816 | <div class="main"> | |
817 | ||
818 | <h3>Identifying keys: Fingerprints and IDs</h3> | |
819 | ||
820 | <p>People's public keys are usually identified by their key fingerprint, | |
821 | which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 | |
822 | (for Edward's key). You can see the fingerprint for your public key, and | |
823 | other public keys saved on your computer, by going to Enigmail → Key | |
824 | Management in your email program's menu, then right clicking on the key | |
825 | and choosing Key Properties. It's good practice to share your fingerprint | |
826 | wherever you share your email address, so that people can double-check that | |
827 | they have the correct public key when they download yours from a keyserver.</p> | |
828 | ||
829 | <p class="notes">You may also see public keys referred to by their key ID, | |
830 | which is simply the last eight digits of the fingerprint, like C09A61E8 for | |
831 | Edward. The key ID is visible directly from the Key Management window. This | |
832 | key ID is like a person's first name (it is a useful shorthand but may not be | |
833 | unique to a given key), whereas the fingerprint actually identifies the key | |
834 | uniquely without the possibility of confusion. If you only have the key ID, | |
835 | you can still look up the key (as well as its fingerprint), like you did in | |
836 | Step 3, but if multiple options appear, you'll need the fingerprint of the | |
837 | person to whom you are trying to communicate to verify which one to use.</p> | |
838 | ||
839 | </div><!-- End .main --> | |
840 | </div><!-- End #step-identify_keys .step--> | |
841 | ||
842 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
843 | <div id="check-ids-before-signing" class="step"> | |
844 | <div class="main"> | |
845 | ||
846 | <h3><em>Important:</em> What to consider when signing keys</h3> | |
847 | ||
848 | <p>Before signing a person's key, you need to be confident that it actually | |
849 | belongs to them, and that they are who they say they are. Ideally, this | |
850 | confidence comes from having interactions and conversations with them over | |
851 | time, and witnessing interactions between them and others. Whenever signing | |
852 | a key, ask to see the full public key fingerprint, and not just the shorter | |
853 | key ID. If you feel it's important to sign the key of someone you've just | |
854 | met, also ask them to show you their government identification, and make | |
855 | sure the name on the ID matches the name on the public key. In Enigmail, | |
856 | answer honestly in the window that pops up and asks "How carefully have you | |
857 | verified that the key you are about to sign actually belongs to the person(s) | |
858 | named above?"</p> | |
859 | ||
860 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
861 | <div class="troubleshooting"> | |
862 | ||
863 | <h4>Advanced</h4> | |
864 | ||
865 | <dl> | |
866 | <dt>Master the Web of Trust</dt> | |
867 | <dd>Unfortunately, trust does not spread between users the way <a | |
868 | href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people | |
869 | think</a>. One of best ways to strengthen the GnuPG community is to deeply <a | |
870 | href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of | |
871 | Trust and to carefully sign as many people's keys as circumstances permit.</dd> | |
872 | ||
873 | <dt>Set ownertrust</dt> | |
874 | <dd>If you trust someone enough to validate other people's keys, you can assign | |
875 | them an ownertrust level through Enigmails's key management window. Right | |
876 | click on the other person's key, go to the "Select Owner Trust" menu option, | |
877 | select the trustlevel and click OK. Only do this once you feel you have a | |
878 | deep understanding of the Web of Trust.</dd> | |
879 | </dl> | |
880 | ||
881 | </div><!-- /.troubleshooting --> | |
882 | </div><!-- End .main --> | |
883 | </div><!-- End #check-ids-before-signing .step--> | |
884 | </div></section><!-- End #section4 --> | |
d85363e7 | 885 | |
39c89f44 TG |
886 | <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ --> |
887 | <section id="section5" class="row"><div> | |
888 | ||
889 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
890 | <div class="section-intro"> | |
891 | ||
892 | <h2><em>#5</em> Use it well</h2> | |
893 | ||
894 | <p>Everyone uses GnuPG a little differently, but it's important to follow | |
895 | some basic practices to keep your email secure. Not following them, you | |
896 | risk the privacy of the people you communicate with, as well as your own, | |
897 | and damage the Web of Trust.</p> | |
898 | ||
899 | </div><!-- End .section-intro --> | |
900 | ||
901 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
902 | <div id="step-5a" class="step"> | |
903 | <div class="sidebar"> | |
904 | ||
905 | <p><img | |
906 | src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png" | |
907 | alt="Section 5: Use it Well (1)" /></p> | |
908 | ||
909 | </div><!-- /.sidebar --> | |
910 | <div class="main"> | |
911 | ||
912 | <h3>When should I encrypt? When should I sign?</h3> | |
913 | ||
914 | <p>The more you can encrypt your messages, the better. If you only encrypt | |
915 | emails occasionally, each encrypted message could raise a red flag for | |
916 | surveillance systems. If all or most of your email is encrypted, people | |
917 | doing surveillance won't know where to start. That's not to say that only | |
918 | encrypting some of your email isn't helpful -- it's a great start and it | |
919 | makes bulk surveillance more difficult.</p> | |
920 | ||
921 | <p>Unless you don't want to reveal your own identity (which requires other | |
922 | protective measures), there's no reason not to sign every message, whether or | |
923 | not you are encrypting. In addition to allowing those with GnuPG to verify | |
924 | that the message came from you, signing is a non-intrusive way to remind | |
925 | everyone that you use GnuPG and show support for secure communication. If you | |
926 | often send signed messages to people that aren't familiar with GnuPG, it's | |
927 | nice to also include a link to this guide in your standard email signature | |
928 | (the text kind, not the cryptographic kind).</p> | |
929 | ||
930 | </div><!-- End .main --> | |
931 | </div><!-- End #step-5a .step --> | |
932 | ||
933 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
934 | <div id="step-5b" class="step"> | |
935 | <div class="sidebar"> | |
936 | ||
937 | <p><img | |
938 | src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" | |
939 | alt="Section 5: Use it Well (2)" /></p> | |
940 | ||
941 | </div><!-- /.sidebar --> | |
942 | <div class="main"> | |
943 | ||
944 | <h3>Be wary of invalid keys</h3> | |
945 | ||
946 | <p>GnuPG makes email safer, but it's still important to watch out for invalid | |
947 | keys, which might have fallen into the wrong hands. Email encrypted with | |
948 | invalid keys might be readable by surveillance programs.</p> | |
949 | ||
950 | <p>In your email program, go back to the first encrypted email that Edward | |
951 | sent you. Because Edward encrypted it with your public key, it will have a | |
952 | message from Enigmail at the top, which most likely says "Enigmail: Part of | |
953 | this message encrypted."</p> | |
954 | ||
955 | <p><b>When using GnuPG, make a habit of glancing at that bar. The program | |
0f3c2a99 | 956 | will warn you there if you get an email signed with a key that can't |
39c89f44 TG |
957 | be trusted.</b></p> |
958 | ||
959 | </div><!-- End .main --> | |
960 | </div><!-- End #step-5b .step --> | |
961 | ||
962 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
963 | <div id="step-5c" class="step"> | |
964 | <div class="main"> | |
965 | ||
966 | <h3>Copy your revocation certificate to somewhere safe</h3> | |
967 | ||
968 | <p>Remember when you created your keys and saved the revocation certificate | |
969 | that GnuPG made? It's time to copy that certificate onto the safest digital | |
970 | storage that you have -- the ideal thing is a flash drive, disk, or hard | |
971 | drive stored in a safe place in your home, not on a device you carry with | |
972 | you regularly.</p> | |
973 | ||
974 | <p>If your private key ever gets lost or stolen, you'll need this certificate | |
975 | file to let people know that you are no longer using that keypair.</p> | |
976 | ||
977 | </div><!-- End .main --> | |
978 | </div><!-- End #step-5c .step --> | |
979 | ||
980 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
981 | <div id="step-lost_key" class="step"> | |
982 | <div class="main"> | |
983 | ||
984 | <h3><em>Important:</em> act swiftly if someone gets your private key</h3> | |
985 | ||
986 | <p>If you lose your private key or someone else gets ahold | |
987 | of it (say, by stealing or cracking your computer), it's | |
988 | important to revoke it immediately before someone else uses | |
989 | it to read your encrypted email or forge your signature. This | |
990 | guide doesn't cover how to revoke a key, but you can follow these <a | |
991 | href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>. | |
992 | After you're done revoking, make a new key and send an email to everyone | |
993 | with whom you usually use your key to make sure they know, including a copy | |
994 | of your new key.</p> | |
995 | ||
996 | </div><!-- End .main --> | |
997 | </div><!-- End #step-lost_key .step--> | |
998 | ||
999 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
1000 | <!---<div id="transfer-key" class="step"> | |
1001 | <div class="main"> | |
1002 | ||
1003 | <h3>Transferring you key</h3> | |
1004 | ||
1005 | <p>You can use Enigmail's <a | |
1006 | href="https://www.enigmail.net/documentation/keyman.php">key management | |
1007 | window</a> to import and export keys. If you want to be able to read | |
1008 | your encrypted email on a different computer, you will need to export | |
1009 | your secret key from here. Be warned, if you transfer the key without <a | |
1010 | href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a> | |
1011 | the drive it's on the transfer will be dramatically less secure.</p> | |
1012 | ||
1013 | </div>--><!-- End .main | |
1014 | </div> End #transfer-key .step--> | |
1015 | ||
1016 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
1017 | <div id="webmail-and-GnuPG" class="step"> | |
1018 | <div class="main"> | |
1019 | ||
1020 | <h3>Webmail and GnuPG</h3> | |
1021 | ||
1022 | <p>When you use a web browser to access your email, you're using webmail, | |
1023 | an email program stored on a distant website. Unlike webmail, your desktop | |
1024 | email program runs on your own computer. Although webmail can't decrypt | |
1025 | encrypted email, it will still display it in its encrypted form. If you | |
1026 | primarily use webmail, you'll know to open your email client when you receive | |
1027 | a scrambled email.</p> | |
1028 | ||
1029 | </div><!-- End .main --> | |
1030 | </div><!-- End #webmail-and-GnuPG .step--> | |
1031 | ||
1032 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ | |
1033 | <div id="step-5d" class="step"> | |
1034 | <div class="main"> | |
1035 | ||
1036 | <h3>Make your public key part of your online identity</h3> | |
1037 | ||
1038 | <p> First add your public key fingerprint to your email signature, then | |
1039 | compose an email to at least five of your friends, telling them you just | |
1040 | set up GnuPG and mentioning your public key fingerprint. Link to this guide | |
1041 | and ask them to join you. Don't forget that there's also an awesome <a | |
1042 | href="infographic.html">infographic to share.</a></p> | |
1043 | ||
1044 | <p class="notes">Start writing your public key fingerprint anywhere someone | |
1045 | would see your email address: your social media profiles, blog, Website, | |
1046 | or business card. (At the Free Software Foundation, we put ours on our | |
1047 | <a href="https://fsf.org/about/staff">staff page</a>.) We need to get our | |
1048 | culture to the point that we feel like something is missing when we see an | |
1049 | email address without a public key fingerprint.</p> | |
1050 | ||
1051 | </div>--><!-- End .main | |
1052 | </div> End #step-5d .step--> | |
1053 | </div></section><!-- End #section5 --> | |
1054 | ||
1055 | <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ --> | |
116f80c3 | 1056 | <section class="row" id="section6"> |
39c89f44 TG |
1057 | <div id="step-click_here" class="step"> |
1058 | <div class="main"> | |
0a225228 | 1059 | |
39c89f44 | 1060 | <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2> |
bb28ee32 | 1061 | |
39c89f44 TG |
1062 | </div><!-- End .main --> |
1063 | </div><!-- End #step-click_here .step--> | |
116f80c3 | 1064 | </section><!-- End #section6 --> |
bdf319c4 | 1065 | |
39c89f44 | 1066 | <!-- ~~~~~~~~~ FAQ ~~~~~~~~~ --> |
f44dd62f | 1067 | <!-- When un-commenting this section go to main.css and search |
116f80c3 | 1068 | for /* Guide Sections Background */ then add #faq to the desired color |
39c89f44 | 1069 | <section class="row" id="faq"><div> |
116f80c3 | 1070 | <div class="sidebar"> |
39c89f44 | 1071 | |
116f80c3 | 1072 | <h2>FAQ</h2> |
6c495e2d | 1073 | |
39c89f44 | 1074 | </div> |
116f80c3 | 1075 | <div class="main"> |
39c89f44 | 1076 | |
116f80c3 ZR |
1077 | <dl> |
1078 | <dt>My key expired</dt> | |
1079 | <dd>Answer coming soon.</dd> | |
6c495e2d | 1080 | |
116f80c3 ZR |
1081 | <dt>Who can read encrypted messages? Who can read signed ones?</dt> |
1082 | <dd>Answer coming soon.</dd> | |
6c495e2d | 1083 | |
39c89f44 TG |
1084 | <dt>My email program is opening at times I don't want it to open/is now my |
1085 | default program and I don't want it to be.</dt> | |
116f80c3 ZR |
1086 | <dd>Answer coming soon.</dd> |
1087 | </dl> | |
39c89f44 | 1088 | |
116f80c3 ZR |
1089 | </div> |
1090 | </div> | |
1091 | </section> --><!-- End #faq --> | |
bdf319c4 | 1092 | |
39c89f44 TG |
1093 | <!-- ~~~~~~~~~ Footer ~~~~~~~~~ --> |
1094 | <footer class="row" id="footer"><div> | |
1095 | <div id="copyright"> | |
1096 | ||
1097 | <h4><a href="https://u.fsf.org/ys"><img | |
1098 | alt="Free Software Foundation" | |
1099 | src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" /></a></h4> | |
1100 | ||
1101 | <p>Copyright © 2014-2016 <a | |
1102 | href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a | |
1103 | href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please | |
1104 | support our work by <a href="https://u.fsf.org/yr">joining us as an associate | |
1105 | member.</a></p> | |
1106 | ||
1107 | <p>The images on this page are under a <a | |
1108 | href="https://creativecommons.org/licenses/by/4.0/">Creative Commons | |
1109 | Attribution 4.0 license (or later version)</a>, and the rest of it is under | |
1110 | a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons | |
1111 | Attribution-ShareAlike 4.0 license (or later version)</a>. Download the <a | |
1112 | href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source | |
1113 | code of Edward reply bot</a> by Andrew Engelbrecht | |
1114 | <sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>, | |
1115 | available under the GNU Affero General Public License. <a | |
1116 | href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these | |
1117 | licenses?</a></p> | |
1118 | ||
1119 | <p>Fonts used in the guide & infographic: <a | |
1120 | href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo | |
1121 | Impallari, <a href="http://www.google.com/fonts/specimen/Signika">Signika</a> | |
1122 | by Anna Giedryś, <a | |
1123 | href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo | |
1124 | Narrow</a> by Omnibus-Type, <a | |
1125 | href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> | |
1126 | by Florian Cramer.</p> | |
1127 | ||
1128 | <p>Download the <a href="emailselfdefense_source.zip">source package</a> | |
1129 | for this guide, including fonts, image source files and the text of Edward's | |
1130 | messages.</p> | |
1131 | ||
1132 | <p>This site uses the Weblabels standard for labeling <a | |
1133 | href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View | |
1134 | the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" | |
1135 | rel="jslicense">source code and license information</a>.</p> | |
1136 | ||
1137 | </div><!-- /#copyright --> | |
1138 | ||
1139 | <p class="credits">Infographic and guide design by <a rel="external" | |
1140 | href="http://jplusplus.org"><strong>Journalism++</strong><img | |
1141 | src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" | |
1142 | alt="Journalism++" /></a></p><!-- /.credits --> | |
1143 | </div></footer><!-- End #footer --> | |
116f80c3 ZR |
1144 | |
1145 | <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script> | |
1146 | <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script> | |
1147 | ||
1148 | <!-- Piwik --> | |
1149 | <script type="text/javascript" > | |
1150 | // @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later | |
1151 | var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/"); | |
1152 | document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E")); | |
1153 | try { | |
1154 | var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13); | |
1155 | piwikTracker.trackPageView(); | |
1156 | piwikTracker.enableLinkTracking(); | |
1157 | } catch( err ) {} | |
1158 | // @license-end | |
1159 | </script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript> | |
1160 | <!-- End Piwik Tracking Code --> | |
1161 | ||
116f80c3 | 1162 | </body> |
bdf319c4 | 1163 | </html> |