update to 4.B troubleshoot adding a manual import for edward when needed
[enc.git] / en / index.html
1 <!DOCTYPE html>
2 <html lang="en">
3 <head>
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, security, GnuPG2, encryption" />
9 <meta name="description" content="Email surveillance violates our fundamental
10 rights and makes free speech risky. This guide will teach you email
11 self-defense in 40 minutes with GnuPG." />
12 <meta name="viewport" content="width=device-width, initial-scale=1" />
13 <link rel="stylesheet" href="../static/css/main.css" />
14 <link rel="shortcut icon"
15 href="../static/img/favicon.ico" />
16 </head>
17 <body>
18 <!--<div style="text-align: center; padding: 2.5px; background-color: #a94442; color:#fcf8e3;"><p>Due to Enigmail's PGP functionality being migrated into Icedove and Thunderbird, steps 2 and 3 of the guide are currently out of date.</p><p> Thank you for your patience while we're working on a new round of updates.</p></div>-->
19
20 <!-- PLACE FUNDRAISER MODAL WINDOW HERE -->
21
22 <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
23 <header class="row" id="header"><div>
24
25
26 <h1>Email Self-Defense</h1>
27
28 <!-- Language list for browsers that do not have JS enabled -->
29 <ul id="languages" class="os">
30 <li><strong><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
31 Translate!</a></strong></li>
32 </ul>
33
34 <ul id="menu" class="os">
35 <li class="spacer"><a href="index.html" class="current">Set up guide</a></li>
36 <!--<li><a href="mac.html">Mac OS</a></li>-->
37 <!--<li><a href="windows.html">Windows</a></li>-->
38 <li class="spacer"><a href="workshops.html">Teach your friends</a></li>
39 <li class="spacer"><a
40 href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email%20encryption%20for%20everyone%20via%20%40fsf">
41 Share&nbsp;
42 <img src="../static/img/gnu-social.png" class="share-logo"
43 alt="[GNU Social]" />&nbsp;
44 <img src="../static/img/mastodon.png" class="share-logo"
45 alt="[Mastodon]" />&nbsp;
46 <img src="../static/img/reddit-alien.png" class="share-logo"
47 alt="[Reddit]" />&nbsp;
48 <img src="../static/img/hacker-news.png" class="share-logo"
49 alt="[Hacker News]" /></a></li>
50 </ul>
51
52 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
53 <div id="fsf-intro">
54
55 <h3><a href="https://u.fsf.org/ys"><img
56 alt="Free Software Foundation"
57 src="../static/img/fsf-logo.png" />
58 </a></h3>
59
60 <div class="fsf-emphasis">
61
62 <p>We fight for computer users' rights, and promote the development of free (as
63 in freedom) software. Resisting bulk surveillance is very important to us.</p>
64
65 <p><strong>Please donate to support Email Self-Defense. We need to keep
66 improving it, and making more materials, for the benefit of people around
67 the world taking the first step towards protecting their privacy.</strong></p>
68
69 </div>
70
71 <p><a
72 href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&amp;id=14&amp;mtm_campaign=email_self_defense&amp;mtm_kwd=guide_donate"><img
73 alt="Donate"
74 src="../static/img/en/donate.png" /></a></p>
75
76 </div><!-- End #fsf-intro -->
77
78 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
79 <div class="intro">
80
81 <p><a id="infographic" href="infographic.html"><img
82 src="../static/img/en/infographic-button.png"
83 alt="View &amp; share our infographic &rarr;" /></a>
84 Bulk surveillance violates our fundamental rights and makes free speech
85 risky. This guide will teach you a basic surveillance self-defense skill: email
86 encryption. Once you've finished, you'll be able to send and receive emails
87 that are scrambled to make sure a surveillance agent or thief intercepting
88 your email can't read them. All you need is a computer with an Internet
89 connection, an email account, and about forty minutes.</p>
90
91 <p>Even if you have nothing to hide, using encryption helps protect the privacy
92 of people you communicate with, and makes life difficult for bulk surveillance
93 systems. If you do have something important to hide, you're in good company;
94 these are the same tools that whistleblowers use to protect their identities
95 while shining light on human rights abuses, corruption, and other crimes.</p>
96
97 <p>In addition to using encryption, standing up
98 to surveillance requires fighting politically for a <a
99 href="https://gnu.org/philosophy/surveillance-vs-democracy.html">reduction
100 in the amount of data collected on us</a>, but the essential first step is
101 to protect yourself and make surveillance of your communication as difficult
102 as possible. This guide helps you do that. It is designed for beginners, but
103 if you already know the basics of GnuPG or are an experienced free software
104 user, you'll enjoy the advanced tips and the <a href="workshops.html">guide
105 to teaching your friends</a>.</p>
106
107 </div><!-- End .intro -->
108 </div></header><!-- End #header -->
109
110 <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
111 <section class="row" id="section1"><div>
112
113 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
114 <div class="section-intro">
115
116 <h2><em>#1</em> Get the pieces</h2>
117
118 <p class="notes">This guide relies on software which is <a
119 href="https://www.gnu.org/philosophy/free-sw.html">freely licensed</a>;
120 it's completely transparent and anyone can copy it or make their
121 own version. This makes it safer from surveillance than proprietary
122 software (like Windows or macOS). Learn more about free software at <a
123 href="https://u.fsf.org/ys">fsf.org</a>.</p>
124
125 <p>Most GNU/Linux operating systems come with GnuPG installed on them, so if you're running one of these systems, you don't have to download it. If you're running macOS or Windows, steps to download GnuPG are below. Before configuring your encryption setup with this guide, though, you'll need a desktop email program installed on your computer. Many GNU/Linux distributions have one installed already, such as Icedove, which may be under the alternate name "Thunderbird." Programs like these are another way to access the same email accounts you can access in a browser (like Gmail), but provide extra features.</p>
126
127 </div><!-- End .section-intro -->
128
129 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
130 <div id="step-1a" class="step">
131 <div class="sidebar">
132
133 <p class="large"><img
134 src="../static/img/en/screenshots/step1a-install-wizard.png"
135 alt="Step 1.A: Install Wizard" /></p>
136
137 </div><!-- /.sidebar -->
138 <div class="main">
139
140 <h3><em>Step 1.a</em> Set up your email program with your email account</h3>
141
142 <p>Open your email program and follow the wizard (step-by-step walkthrough)
143 that sets it up with your email account. This usually starts from "Account Settings" &rarr; "Add Mail Account". You should get the email server settings from your systems administrator or the help section of your email account.</p>
144
145
146 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
147 <div class="troubleshooting">
148
149 <h4>Troubleshooting</h4>
150
151 <dl>
152 <dt>The wizard doesn't launch</dt>
153 <dd>You can launch the wizard yourself, but the menu option for doing so is
154 named differently in each email program. The button to launch it will be in
155 the program's main menu, under "New" or something similar, titled something
156 like "Add account" or "New/Existing email account."</dd>
157
158 <dt>The wizard can't find my account or isn't downloading my mail</dt>
159 <dd>Before searching the Web, we recommend you start by asking other people
160 who use your email system, to figure out the correct settings.</dd>
161
162 <dt>I can't find the menu</dt>
163 <dd>In many new email programs, the main menu is represented by an image of
164 three stacked horizontal bars.</dd>
165
166 <dt class="feedback">Don't see a solution to your problem?</dt>
167 <dd class="feedback">Please let us know on the <a
168 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
169 page</a>.</dd>
170 </dl>
171
172 </div><!-- /.troubleshooting -->
173 </div><!-- End .main -->
174 </div><!-- End #step1-a .step -->
175
176 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
177 <div id="step-1b" class="step">
178 <div class="main">
179
180 <h3><em>Step 1.b</em> Install GnuPG</h3>
181
182 <p>If you are using a GNU/Linux machine, you should already have GnuPG installed, and you can skip to <a href="#section2">Section 2</a>.</p>
183
184 <p>If you are using a macOS or Windows machine, however, you need to first install the GnuPG program. Select your operating system below and follow the instructions. For the rest of this guide, the steps are the same for all operating systems. </p>
185
186 <!-- ~~~~~~~~~ MACOS ~~~~~~~~~ -->
187 <div class="troubleshooting">
188
189 <h4>macOS</h4>
190
191 <dl>
192 <dt>Use a third-party package manager to install GnuPG</dt>
193 <dd>
194 <p>The default macOS package manager makes it difficult to install GnuPG and other pieces of free software (like Emacs, GIMP, or Inkscape). To make things easier, we recommend setting up the third-party package manager "Homebrew" to install GnuPG. For this, we will use a program called "Terminal," which is pre-installed on macOS.</p>
195
196 <p># Copy the first command on the home page of <a href="https://brew.sh/">Homebrew</a> by clicking on the clipboard icon, and paste it in Terminal. Click "Enter" and wait for the installation to finalize.</p>
197 <p># Then install GnuPG by entering the following code in Terminal:<br/>
198 <code>brew install gnupg gnupg2</code></p>
199 </dd>
200 </dl>
201
202 </div><!-- /.troubleshooting -->
203
204 <!-- ~~~~~~~~~ WINDOWS ~~~~~~~~~ -->
205 <div class="troubleshooting">
206
207 <h4>Windows</h4>
208
209 <dl>
210 <dt>Get GnuPG by downloading GPG4Win</dt>
211 <dd><p><a href="https://www.gpg4win.org/">GPG4Win</a> is an email and file encryption software package that includes GnuPG. Download and install the latest version, choosing default options whenever asked. After it's installed, you can close any windows that it creates.</p>
212 </dd>
213 </dl>
214
215 </div><!-- /.troubleshooting -->
216 </div><!-- End .main -->
217 </div><!-- End #step1-b .step -->
218
219 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
220 <div id="terminology" class="step">
221 <div class="main">
222
223 <h3>GnuPG, OpenPGP, what?</h3>
224
225 <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP
226 are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the
227 encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG)
228 is the program that implements the standard. Most email programs provide an interface for GnuPG. There is also a newer version of GnuPG, called GnuPG2.</p>
229
230 </div><!-- End .main -->
231 </div><!-- End #terminology.step-->
232
233 </div></section><!-- End #section1 -->
234
235 <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
236 <section id="section2" class="row"><div>
237
238 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
239 <div class="section-intro">
240
241 <h2><em>#2</em> Make your keys</h2>
242 <p class="float medium"><img src="../static/img/en/screenshots/step2a-01-make-keypair.png" alt="A robot with a head shaped like a key holding a private and a public key"/></p>
243
244 <p>To use the GnuPG system, you'll need a public key and a private key (known
245 together as a keypair). Each is a long string of randomly generated numbers
246 and letters that are unique to you. Your public and private keys are linked
247 together by a special mathematical function.</p>
248
249 <p>Your public key isn't like a physical key, because it's stored in the open
250 in an online directory called a keyserver. People download it and use it,
251 along with GnuPG, to encrypt emails they send to you. You can think of the
252 keyserver as a phonebook; people who want to send you encrypted email can
253 look up your public key.</p>
254
255 <p>Your private key is more like a physical key, because you keep it to
256 yourself (on your computer). You use GnuPG and your private key together to
257 descramble encrypted emails other people send to you. <strong>You should never share your private key with anyone, under any
258 circumstances.</strong></p>
259
260 <p>In addition to encryption and decryption, you can also use these keys to
261 sign messages and check the authenticity of other people's signatures. We'll
262 discuss this more in the next section.</p>
263
264 </div><!-- End .section-intro -->
265
266 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
267 <div id="step-2a" class="step">
268 <div class="sidebar">
269 <p class="large"><img
270 src="../static/img/en/screenshots/step2a-02-make-keypair.png"
271 alt="Step 2.A: Make your Keypair" /></p>
272
273 <p class="large"><img
274 src="../static/img/en/screenshots/step2a-03-make-keypair.png"
275 alt="Step 2.A: Set your passphrase" /></p>
276
277 </div><!-- /.sidebar -->
278 <div class="main">
279
280 <h3><em>Step 2.a</em> Make a keypair</h3>
281
282 <h4>Make your keypair</h4>
283
284 <p>We will use the command line in a terminal to create a keypair using the
285 GnuPG program.</p>
286
287 <p class="notes">Whether on GNU/Linux, macOS or Windows, you can launch your
288 terminal ("Terminal" in macOS, "PowerShell" in Windows) from the Applications
289 menu (some GNU/Linux systems respond to the <kbd>Ctrl + Alt + T</kbd>
290 shortcut).</p>
291
292 <p># Enter <code>gpg --full-generate-key</code> to start the process.</p>
293 <p># To answer what kind of key you would like to create, select the default option: <samp>1&nbsp;RSA&nbsp;and&nbsp;RSA</samp>.</p>
294 <p># Enter the following keysize: <code>4096</code> for a strong key.</p>
295 <p># Choose the expiration date; we suggest <code>2y</code> (2 years).</p>
296 <p>Follow the prompts to continue setting up with your personal details.</p>
297
298 <h4>Set your passphrase</h4>
299 <p>On the screen titled "Passphrase," pick a strong password! You can
300 do it manually, or you can use the Diceware method. Doing it manually
301 is faster but not as secure. Using Diceware takes longer and requires
302 dice, but creates a password that is much harder for attackers to figure
303 out. To use it, read the section "Make a secure passphrase with Diceware" in <a
304 href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">
305 this article</a> by Micah Lee.</p>
306
307
308 <p>If you'd like to pick a passphrase manually, come up with something
309 you can remember which is at least twelve characters long, and includes
310 at least one lower case and upper case letter and at least one number or
311 punctuation symbol. Never pick a password you've used elsewhere. Don't use
312 any recognizable patterns, such as birthdays, telephone numbers, pets' names,
313 song lyrics, quotes from books, and so on.</p>
314
315 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
316 <div class="troubleshooting">
317
318 <h4>Troubleshooting</h4>
319 <dl>
320 <dt>GnuPG is not installed</dt>
321 <dd>
322 You can check if this is the case with the command <code>gpg --version</code>&#65279;.
323 If GnuPG is not installed, it will bring up the following result on most GNU/Linux operating systems, or something like it:
324 <samp>Command 'gpg' not found, but can be installed with:
325 sudo apt install gnupg</samp>. Follow that command and install the program.</dd>
326
327 <dt>I took too long to create my passphrase</dt>
328 <dd>That's okay. It's important to think about your passphrase. When you're ready, just follow the steps from the beginning again to create your key.</dd>
329
330 <dt>How can I see my key?</dt>
331 <dd>
332 Use the following command to see all keys: <code>gpg --list-keys</code>&#65279;. Yours should be listed in there, and later, so will Edward's (<a href="#section3">Section 3</a>).<br />
333 If you want to see only your key, you can use <code>gpg --list-key [your@email]</code>&#65279;.<br />
334 You can also use <code>gpg --list-secret-key</code> to see your own private key.</dd>
335
336 <dt>More resources</dt>
337 <dd>For more information about this process, you can also refer to <a
338 href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy
339 Handbook</a>. Make sure you stick with "RSA and RSA" (the default),
340 because it's newer and more secure than the algorithms the documentation
341 recommends. Also make sure your key is at least 4096&nbsp;bits if you
342 want to be secure.</dd>
343
344 <dt class="feedback">Don't see a solution to your problem?</dt>
345 <dd class="feedback">Please let us know on the <a
346 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
347 page</a>.</dd>
348 </dl>
349
350 </div><!-- /.troubleshooting -->
351
352 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
353 <div class="troubleshooting">
354
355 <h4>Advanced</h4>
356 <dl>
357 <dt>Advanced key pairs</dt>
358 <dd>When GnuPG creates a new keypair, it compartmentalizes
359 the encryption function from the signing function through <a
360 href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use
361 subkeys carefully, you can keep your GnuPG identity more
362 secure and recover from a compromised key much more quickly. <a
363 href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a>
364 and <a href="https://keyring.debian.org/creating-key.html">the Debian wiki</a>
365 provide good guides for setting up a secure subkey configuration.</dd>
366 </dl>
367
368 </div><!-- /.troubleshooting -->
369 </div><!-- End .main -->
370 </div><!-- End #step-2a .step -->
371
372 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
373 <div id="step-2b" class="step">
374 <div class="sidebar">
375 <p class="large"><img
376 src="../static/img/en/screenshots/step2b-04-upload-and-certificate.png"
377 alt="Step 2.B: Send to server and generate a certificate" /></p>
378
379 </div><!-- /.sidebar -->
380 <div class="main">
381
382 <h3><em>Step 2.b</em> Some important steps following creation</h3>
383
384 <h4>Upload your key to a keyserver</h4>
385 <p>We will upload your key to a keyserver, so if someone wants to send you an encrypted message, they can download your public key from the Internet. There are multiple keyservers
386 that you can select from the menu when you upload, but they are all copies
387 of each other, so it doesn't matter which one you use. However, it sometimes
388 takes a few hours for them to match each other when a new key is uploaded.</p>
389 <p># Copy your keyID: <code>gpg --list-key [your@email]</code> will list your public ("pub") key information, including your keyID, which is a unique list of numbers and letters. Copy this keyID, so you can use it in the following command.</p>
390 <p># Upload your key to a server:
391 <code>gpg --send-key [keyID]</code></p>
392
393 <h4>Export your key to a file</h4>
394 <p>Use the following command to export your secret key so you can import it into your email client at the next <a href="#section3">step</a>. To avoid getting your key compromised, store this in a safe place, and make sure that if it is transferred, it is done so in a trusted way. Exporting your keys can be done with the following commands:</p>
395 <p><code>
396 $ gpg --export-secret-keys -a [keyID] > my_secret_key.asc<br/>
397 $ gpg --export -a [keyID] > my_public_key.asc
398 </code></p>
399
400 <h4>Generate a revocation certificate</h4>
401 <p>Just in case you lose your key, or it gets compromised, you want to generate a certificate and choose to save it in a safe place on your computer for now (please refer to <a href="#step-6c">Step 6.C</a> for how to best store your revocation cerficate safely). This step is essential for your email self-defense, as you'll learn more about in <a href="#section5">Section 5</a>.</p>
402
403 <p># Copy your keyID: <code>gpg --list-key [your@email]</code> will list your public ("pub") key information, including your keyID, which is a unique list of numbers and letters. Copy this keyID, so you can use it in the following command.</p>
404 <p># Generate a revocation certificate: <code>gpg --gen-revoke --output revoke.asc [keyID]</code></p>
405 <p># It will prompt you to give a reason for revocation, we recommend to use <samp>1&nbsp;=&nbsp;key has been compromised</samp>.</p>
406 <p># You don't have to fill in a reason, but you can; then press "Enter" for an empty line, and confirm your selection.</p>
407
408
409 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
410 <div class="troubleshooting">
411
412 <h4>Troubleshooting</h4>
413
414 <dl>
415 <dt>My key doesn't seem to be working or I get a "permission denied."</dt>
416 <dd><p>Like every other file or folder, gpg keys are subject to permissions. If these are not set correctly, your system may not be accepting your keys. You can follow the next steps to check, and update to the right permissions.</p>
417
418 <p># Check your permissions: <code>ls -l ~/.gnupg/*</code></p>
419 <p># Set permissions to read, write, execute for only yourself, no others. These are the recommended permissions for your folder. <br/>
420 You can use the code: <code>chmod 700 ~/.gnupg</code></p>
421 <p># Set permissions to read and write for yourself only, no others. These are the recommended permissions for the keys inside your folder. <br/>
422 You can use the code: <code>chmod 600 ~/.gnupg/*</code></p>
423
424 <p class="notes">If you have (for any reason) created your own folders inside ~/.gnupg, you must also additionally apply execute permissions to that folder. Folders require execution privileges to be opened. For more information on permissions, you can check out <a href="https://helpdeskgeek.com/linux-tips/understanding-linux-permissions-chmod-usage/">this detailed information guide</a>.</p>
425 </dd>
426 <dt class="feedback">Don't see a solution to your problem?</dt>
427 <dd class="feedback">Please let us know on the <a
428 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
429 page</a>.</dd>
430 </dl>
431
432 </div><!-- /.troubleshooting -->
433
434 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
435 <div class="troubleshooting">
436
437 <h4>Advanced</h4>
438
439 <dl>
440 <dt>More about keyservers</dt>
441 <dd>You can find some more keyserver information<a
442 href="https://www.gnupg.org/gph/en/manual/x457.html"> in this manual</a>. <a
443 href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a>
444 maintains a list of highly interconnected keyservers. You can also <a
445 href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export
446 your key</a> as a file on your computer.</dd>
447
448 <dt>Transferring your keys</dt>
449 <dd>
450 <p>Use the following commands to transfer your keys. To avoid getting your key compromised, store it in a safe place, and make sure that if it is transferred, it is done so in a trusted way. Importing and exporting a key can be done with the following commands:</p>
451
452 <p><code>
453 $ gpg --export-secret-keys -a [keyID] > my_private_key.asc<br />
454 $ gpg --export -a [keyID] > my_public_key.asc<br />
455 $ gpg --import my_private_key.asc<br />
456 $ gpg --import my_public_key.asc
457 </code></p>
458
459 <p>Ensure that the keyID printed is the correct one, and if so, then go ahead and add ultimate trust for it:</p>
460
461 <p><code>
462 $ gpg --edit-key [your@email]
463 </code></p>
464
465 <p>Because this is your key, you should choose <code>ultimate</code>&#65279;. You shouldn't trust anyone else's key ultimately.</p>
466
467 <p class="notes"> Refer to <a href="#step-2b">Troubleshooting in Step 2.B</a> for more information on permissions. When transferring keys, your permissions may get mixed, and errors may be prompted. These are easily avoided when your folders and files have the right permissions</p>
468 </dd>
469 </dl>
470
471 </div><!-- /.troubleshooting -->
472 </div><!-- End .main -->
473 </div><!-- End #step-2b .step -->
474 </div></section><!-- End #section2 -->
475
476 <!-- ~~~~~~~~~ Section 3: Set up email encryption ~~~~~~~~~ -->
477 <section id="section3" class="row"><div>
478
479 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
480 <div class="section-intro">
481
482 <h2><em>#3</em> Set up email encryption</h2>
483 <p class="notes">The Icedove (or Thunderbird) email program has PGP functionality integrated, which makes it pretty easy to work with. We'll take you through the steps of integrating and using your key in these email clients.</p>
484
485 </div><!-- End .section-intro -->
486
487 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
488 <div id="step-3a" class="step">
489 <div class="sidebar">
490
491 <p class="large"><img src="../static/img/en/screenshots/step3a-open-key-manager.png"
492 alt="Step 3.A: Email Menu" /></p>
493
494 <p class="large"><img src="../static/img/en/screenshots/step3a-import-from-file.png"
495 alt="Step 3.A: Import From File" /></p>
496
497 <p class="large"><img src="../static/img/en/screenshots/step3a-success.png"
498 alt="Step 3.A: Success" /></p>
499
500 <p class="large"><img src="../static/img/en/screenshots/step3a-troubleshoot.png"
501 alt="Step 3.A: Troubleshoot" /></p>
502 </div><!-- /.sidebar -->
503 <div class="main">
504
505 <h3><em>Step 3.a</em> Set up your email with encryption</h3>
506
507 <p>Once you have set up your email with encryption, you can start contributing to encrypted traffic on the Internet. First we'll get your email client to import your secret key, and we will also learn how to get other people's public keys from servers so you can send and receive encrypted email.</p>
508
509 <p># Open your email client and use "Tools" &rarr; <i>OpenPGP Key Manager</i></p>
510 <p># Under "File" &rarr; <i>Import Secret Key(s) From File</i></p>
511 <p># Select the file you saved under the name [my_secret_key.asc] in <a href="#step-2b">Step 2.B</a> when you exported your key</p>
512 <p># Unlock with your passphrase</p>
513 <p># You will receive a "OpenPGP keys successfully imported" window to confirm success</p>
514 <p># Go to "Account settings" &rarr; "End-To-End Encryption," and make sure your key is imported and select <i>Treat this key as a Personal Key</i>.</p>
515
516 </div><!-- End .main -->
517
518 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
519 <div class="main">
520 <div class="troubleshooting">
521 <h4>Troubleshooting</h4>
522 <dl>
523 <dt>I'm not sure the import worked correctly</dt>
524 <dd>
525 Look for "Account settings" &rarr; "End-To-End Encryption." Here you can see if your personal key associated with this email is found. If it is not, you can try again via the <i>Add key</i> option. Make sure you have the correct, active, secret key file.
526 </dd>
527
528 <dt class="feedback">Don't see a solution to your problem?</dt>
529 <dd class="feedback">Please let us know on the <a
530 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
531 page</a>.</dd>
532 </dl>
533
534 </div><!-- /.troubleshooting -->
535 </div><!-- End .main -->
536 </div><!-- End #step3-a .step -->
537 </div></section><!-- End #section3 -->
538
539 <!-- ~~~~~~~~~ Section 4: Try it out ~~~~~~~~~ -->
540 <section class="row" id="section4"><div>
541
542 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
543 <div class="section-intro">
544
545 <h2><em>#4</em> Try it out!</h2>
546 <p class="float small"><img src="../static/img/en/screenshots/section3-try-it-out.png" alt="Illustration of a person in a house with a cat connected to a server"/></p>
547 <p>Now you'll try a test correspondence with an FSF computer program named Edward,
548 who knows how to use encryption. Except where noted, these are the same
549 steps you'd follow when corresponding with a real, live person.</p>
550
551 <!-- <p>NOTE: Edward is currently having some technical difficulties, so he
552 may take a long time to respond, or not respond at all. We're sorry about
553 this and we're working hard to fix it. Your key will still work even without
554 testing with Edward.</p> -->
555
556 <div style="clear: both"></div>
557 </div><!-- End .section-intro -->
558
559 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
560 <div id="step-4a" class="step">
561 <div class="sidebar">
562
563 <p class="large"><img
564 src="../static/img/en/screenshots/step4a-send-key-to-Edward.png"
565 alt="Step 4.A Send key to Edward." /></p>
566
567 </div><!-- /.sidebar -->
568 <div class="main">
569
570 <h3><em>Step 4.a</em> Send Edward your public key</h3>
571
572 <p>This is a special step that you won't have to do when corresponding
573 with real people. In your email program's menu, go to "Tools" &rarr; "OpenPGP Key
574 Manager." You should see your key in the list that pops up. Right click
575 on your key and select <i>Send Public Keys by Email</i>. This will create a new draft message, as if you had just hit the "Write" button, but in the attachment you will find your public keyfile.</p>
576
577 <p>Address the message to <a
578 href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word
579 (whatever you want) in the subject and body of the email. Don't send yet.</p>
580
581 <p>We want Edward to be able to open the email with your keyfile, so we want this first special message to be unencrypted. Make sure encryption is turned off by using the dropdown menu "Security" and select <i>Do Not Encrypt</i>. Once encryption is off, hit Send.</p>
582
583 <p class="notes">It may take two or three minutes for Edward to
584 respond. In the meantime, you might want to skip ahead and check out the <a
585 href="#section6">Use it Well</a> section of this guide. Once you have received a response,
586 head to the next step. From here on, you'll be doing just the same thing as
587 when corresponding with a real person.</p>
588
589 <p>When you open Edward's reply, GnuPG may prompt you for your passphrase
590 before using your private key to decrypt it.</p>
591
592 </div><!-- End .main -->
593 </div><!-- End #step-4a .step -->
594
595 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
596 <div id="step-4b" class="step">
597 <div class="sidebar">
598
599 <p class="large"><img
600 src="../static/img/en/screenshots/step4b-option1-verify-key.png"
601 alt="Step 4.B Option 1. Verify key" /></p>
602
603 <p class="large"><img
604 src="../static/img/en/screenshots/step4b-option2-import-key.png"
605 alt="Step 4.B Option 2. Import key" /></p>
606 </div><!-- /.sidebar -->
607
608 <div class="main">
609
610 <h3><em>Step 4.b</em> Send a test encrypted email</h3>
611
612 <h4>Get Edward's key</h4>
613
614 <p>To encrypt an email to Edward, you need its public key, so now you'll have
615 to download it from a keyserver. You can do this in two different ways:</p>
616 <p><strong>Option 1.</strong> In the email answer you received from Edward as a response to your first email, Edward's public key was included. On the right of the email, just above the writing area, you will find an "OpenPGP" button that has a lock and a little wheel next to it. Click that, and select <i>Discover</i> next to the text: "This message was signed with a key that you don't yet have." A popup with Edward's key details will follow.</p>
617
618 <p><strong>Option 2.</strong> Open your OpenPGP Key manager, and under "Keyserver" choose <i>Discover Keys Online</i>. Here, fill in Edward's email address, and import Edward's key.</p>
619
620 <p>The option <i>Accepted (unverified)</i> will add this key to your key manager, and now it can be used to send encrypted emails and to verify digital signatures from Edward.</p>
621
622 <p class="notes">In the popup window confirming if you want to import Edward's key, you'll see many different emails that are all associated with its key. This is correct; you can safely import the key.</p>
623
624 <p class="notes">Since you encrypted this email with Edward's public key,
625 Edward's private key is required to decrypt it. Edward is the only one with
626 its private key, so no one except Edward can decrypt it.</p>
627
628 <h4>Send Edward an encrypted email</h4>
629
630 <p> Write a new email in your email program, addressed to <a
631 href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject
632 "Encryption test" or something similar and write something in the body.</p>
633
634 <p>This time, make sure encryption is turned on by using the dropdown menu "Security" and select <i>Require Encryption</i>. Once encryption is on, hit Send.</p>
635
636
637 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
638 <div class="troubleshooting">
639
640 <h4>Troubleshooting</h4>
641
642 <dl>
643 <dt>"Recipients not valid, not trusted or not found"</dt>
644 <dd>You could get the above error message, or something along these lines: "Unable to send this message with end-to-end encryption, because there are problems with the keys of the following recipients: ..." In these cases, you may be trying to send an encrypted email to someone when you do not have their public key yet. Make sure you follow the steps above to import the key to your key manager. Open OpenPGP Key Manager to make sure the recipient is listed there.</dd>
645
646 <dt>Unable to send message</dt>
647 <dd>You could get the following message when trying to send your encrypted email: "Unable to send this message with end-to-end encryption, because there are problems with the keys of the following recipients: edward-en@fsf.org." This usually means you imported the key with the "unaccepted (unverified) option." Go to the "key properties" of this key by right clicking on the key in the OpenPGP Key Manager, and select the option <i>Yes, but I have not verified that this is the correct key</i> in the "Acceptance" option at the bottom of this window. Resend the email.</dd>
648
649 <dt>I can't find Edward's key</dt>
650 <dd>Close the pop-ups that have appeared since you clicked Send. Make sure
651 you are connected to the Internet and try again. If that doesn't work, you can download the key manually from <a href="https://keys.openpgp.org/search?q=edward-en%40fsf.org">the keyserver</a>, and import it by using the <i>Import Public Key(s) from File</i> option in the <i>OpenPGP Key Manager</i>.</dd>
652
653 <dt>Unscrambled messages in the Sent folder</dt>
654 <dd>Even though you can't decrypt messages encrypted to someone else's key,
655 your email program will automatically save a copy encrypted to your public key,
656 which you'll be able to view from the Sent folder like a normal email. This
657 is normal, and it doesn't mean that your email was not sent encrypted.</dd>
658
659 <dt class="feedback">Don't see a solution to your problem?</dt>
660 <dd class="feedback">Please let us know on the <a
661 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
662 page</a>.</dd>
663 </dl>
664
665 </div><!-- /.troubleshooting -->
666
667 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
668 <div class="troubleshooting">
669
670 <h4>Advanced</h4>
671
672 <dl>
673 <dt>Encrypt messages from the command line</dt>
674 <dd>You can also encrypt and decrypt messages and files from the <a
675 href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>,
676 if that's your preference. The option --armor makes the encrypted output
677 appear in the regular character set.</dd>
678 </dl>
679
680 </div><!-- /.troubleshooting -->
681 </div><!-- End .main -->
682 </div><!-- End #step-4b .step -->
683
684 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
685 <div id="step-headers_unencrypted" class="step">
686 <div class="main">
687
688 <h3><em>Important:</em> Security tips</h3>
689
690 <p>Even if you encrypt your email, the subject line is not encrypted, so
691 don't put private information there. The sending and receiving addresses
692 aren't encrypted either, so a surveillance system can still figure out who
693 you're communicating with. Also, surveillance agents will know that you're
694 using GnuPG, even if they can't figure out what you're saying. When you
695 send attachments, you can choose to encrypt them or not,
696 independent of the actual email.</p>
697
698 <p>For greater security against potential attacks, you can turn off
699 HTML. Instead, you can render the message body as plain text. In order
700 to do this in Icedove or Thunderbird, go to "View" &rarr; "Message Body As" &rarr; <i>Plain
701 Text</i>.</p>
702
703 </div><!-- End .main -->
704 </div><!-- End #step-headers_unencrypted .step-->
705
706 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
707 <div id="step-4c" class="step">
708 <div class="sidebar">
709
710 <p class="large"><img
711 src="../static/img/en/screenshots/step4c-Edward-response.png"
712 alt="Step 4.C Edward's response" /></p>
713
714 </div><!-- /.sidebar -->
715
716 <div class="main">
717
718 <h3><em>Step 4.c</em> Receive a response</h3>
719
720 <p>When Edward receives your email, it will use its private key to decrypt
721 it, then reply to you. </p>
722
723 <p class="notes">It may take two or three minutes for Edward to
724 respond. In the meantime, you might want to skip ahead and check out the <a
725 href="#section6">Use it Well</a> section of this guide.</p>
726
727 <p>Edward will send you an encrypted email back saying your email was received and decrypted. Your email client will automatically decrypt Edward's message.</p>
728
729 <p class="notes">The OpenPGP button in the email will show a little green checkmark over the lock symbol to show the message is encrypted, and a little orange warning sign which means that you have accepted the key, but not verified it. When you have not yet accepted the key, you will see a little question mark there. Clicking the prompts in this button will lead you to key properties as well.</p>
730
731 </div><!-- End .main -->
732 </div><!-- End #step-4c .step -->
733
734 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
735 <div id="step-4d" class="step">
736 <div class="main">
737
738 <h3><em>Step 4.d</em> Send a signed test email</h3>
739
740 <p>GnuPG includes a way for you to sign messages and files, verifying that
741 they came from you and that they weren't tampered with along the way. These
742 signatures are stronger than their pen-and-paper cousins -- they're impossible
743 to forge, because they're impossible to create without your private key
744 (another reason to keep your private key safe).</p>
745
746 <p>You can sign messages to anyone, so it's a great way to make people
747 aware that you use GnuPG and that they can communicate with you securely. If
748 they don't have GnuPG, they will be able to read your message and see your
749 signature. If they do have GnuPG, they'll also be able to verify that your
750 signature is authentic.</p>
751
752 <p>To sign an email to Edward, compose any message to the email address and click the
753 pencil icon next to the lock icon so that it turns gold. If you sign a
754 message, GnuPG may ask you for your password before it sends the message,
755 because it needs to unlock your private key for signing.</p>
756
757 <p>In "Account Settings" &rarr; "End-To-End-Encryption" you can opt to <i>add digital signature by default</i>.</p>
758
759 </div><!-- End .main -->
760 </div><!-- End #step-4d .step -->
761
762 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
763 <div id="step-4e" class="step">
764 <div class="main">
765
766 <h3><em>Step 4.e</em> Receive a response</h3>
767
768 <p>When Edward receives your email, he will use your public key (which
769 you sent him in <a href="#step-3a">Step 3.A</a>) to verify the message
770 you sent has not been tampered with and to encrypt a reply to you.</p>
771
772 <p class="notes">It may take two or three minutes for Edward to
773 respond. In the meantime, you might want to skip ahead and check out the <a
774 href="#section6">Use it Well</a> section of this guide.</p>
775
776 <p>Edward's reply will arrive encrypted, because he prefers to use encryption
777 whenever possible. If everything goes according to plan, it should say
778 "Your signature was verified." If your test signed email was also encrypted,
779 he will mention that first.</p>
780
781 <p>When you receive Edward's email and open it, your email client will
782 automatically detect that it is encrypted with your public key, and
783 then it will use your private key to decrypt it.</p>
784
785 </div><!-- End .main -->
786 </div><!-- End #step-4e .step -->
787 </div></section>
788
789 <!-- ~~~~~~~~~ Section 5: Learn About the Web of Trust ~~~~~~~~~ -->
790 <section class="row" id="section5"><div>
791
792 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
793 <div class="section-intro">
794
795 <h2><em>#5</em> Learn about the Web of Trust</h2>
796 <p class="float small"><img src="../static/img/en/screenshots/section5-web-of-trust.png" alt="Illustration of keys all interconnected with a web of lines"/></p>
797
798 <p>Email encryption is a powerful technology, but it has a weakness:
799 it requires a way to verify that a person's public key is actually
800 theirs. Otherwise, there would be no way to stop an attacker from making
801 an email address with your friend's name, creating keys to go with it, and
802 impersonating your friend. That's why the free software programmers that
803 developed email encryption created keysigning and the Web of Trust.</p>
804
805 <p>When you sign someone's key, you are publicly saying that you've verified
806 that it belongs to them and not someone else.</p>
807
808 <p>Signing keys and signing messages use the same type of mathematical
809 operation, but they carry very different implications. It's a good practice
810 to generally sign your email, but if you casually sign people's keys, you
811 may accidentally end up vouching for the identity of an imposter.</p>
812
813 <p>People who use your public key can see who has signed it. Once you've
814 used GnuPG for a long time, your key may have hundreds of signatures. You
815 can consider a key to be more trustworthy if it has many signatures from
816 people that you trust. The Web of Trust is a constellation of GnuPG users,
817 connected to each other by chains of trust expressed through signatures.</p>
818
819 </div><!-- End .section-intro -->
820
821 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
822 <div id="step-5a" class="step">
823 <div class="sidebar">
824
825 <p class="large"><img
826 src="../static/img/en/screenshots/step5a-key-properties.png"
827 alt="Section 5: trusting a key" /></p>
828
829 </div><!-- /.sidebar -->
830 <div class="main">
831
832 <h3><em>Step 5.a</em> Sign a key</h3>
833
834 <p>In your email program's menu, go to OpenPGP Key Manager and select <i>Key properties</i> by right clicking on Edward's key.</p>
835
836 <p>Under "Your Acceptance," you can select <i>Yes, I've verified in person this key has the correct fingerprint"</i>.</p>
837
838 <p class="notes">You've just effectively said "I trust that Edward's public
839 key actually belongs to Edward." This doesn't mean much because Edward isn't
840 a real person, but it's good practice, and for real people it is important. You can read more about signing a person's key in the <a href="#check-ids-before-signing">check IDs before signing</a> section.</p>
841
842 <!--<div id="pgp-pathfinder">
843
844 <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi"
845 method="get">
846
847 <p><strong>From:</strong><input type="text" value="xD41A008"
848 name="FROM"></p>
849
850 <p><strong>To:</strong><input type="text" value="50BD01x4" name="TO"></p>
851
852 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"><input
853 type="reset" value="reset" name=".reset"></p>
854
855 </form>
856
857 </div>End #pgp-pathfinder -->
858 </div><!-- End .main -->
859 </div><!-- End #step-5a .step -->
860
861 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
862 <div id="step-identify_keys" class="step">
863 <div class="main">
864
865 <h3>Identifying keys: Fingerprints and IDs</h3>
866
867 <p>People's public keys are usually identified by their key fingerprint,
868 which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8
869 (for Edward's key). You can see the fingerprint for your public key, and
870 other public keys saved on your computer, by going to OpenPGP Key
871 Management in your email program's menu, then right clicking on the key
872 and choosing Key Properties. It's good practice to share your fingerprint
873 wherever you share your email address, so that people can double-check that
874 they have the correct public key when they download yours from a keyserver.</p>
875
876 <p class="notes">You may also see public keys referred to by a shorter
877 keyID. This keyID is visible directly from the Key Management
878 window. These eight character keyIDs were previously used for
879 identification, which used to be safe, but is no longer reliable. You
880 need to check the full fingerprint as part of verifying you have the
881 correct key for the person you are trying to contact. Spoofing, in
882 which someone intentionally generates a key with a fingerprint whose
883 final eight characters are the same as another, is unfortunately
884 common.</p>
885
886 </div><!-- End .main -->
887 </div><!-- End #step-identify_keys .step-->
888
889 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
890 <div id="check-ids-before-signing" class="step">
891 <div class="main">
892
893 <h3><em>Important:</em> What to consider when signing keys</h3>
894
895 <p>Before signing a person's key, you need to be confident that it actually
896 belongs to them, and that they are who they say they are. Ideally, this
897 confidence comes from having interactions and conversations with them over
898 time, and witnessing interactions between them and others. Whenever signing
899 a key, ask to see the full public key fingerprint, and not just the shorter
900 keyID. If you feel it's important to sign the key of someone you've just
901 met, also ask them to show you their government identification, and make
902 sure the name on the ID matches the name on the public key.</p>
903
904 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
905 <div class="troubleshooting">
906
907 <h4>Advanced</h4>
908
909 <dl>
910 <dt>Master the Web of Trust</dt>
911 <dd>Unfortunately, trust does not spread between users the way <a
912 href="https://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people
913 think</a>. One of the best ways to strengthen the GnuPG community is to deeply <a
914 href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of
915 Trust and to carefully sign as many people's keys as circumstances permit.</dd>
916 </dl>
917
918 </div><!-- /.troubleshooting -->
919 </div><!-- End .main -->
920 </div><!-- End #check-ids-before-signing .step-->
921 </div></section><!-- End #section5 -->
922
923 <!-- ~~~~~~~~~ Section 6: Use it well ~~~~~~~~~ -->
924 <section id="section6" class="row"><div>
925
926 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
927 <div class="section-intro">
928
929 <h2><em>#6</em> Use it well</h2>
930
931 <p>Everyone uses GnuPG a little differently, but it's important to follow
932 some basic practices to keep your email secure. Not following them, you
933 risk the privacy of the people you communicate with, as well as your own,
934 and damage the Web of Trust.</p>
935
936 </div><!-- End .section-intro -->
937
938 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
939 <div id="step-6a" class="step">
940 <div class="sidebar">
941
942 <p class="medium"><img
943 src="../static/img/en/screenshots/section6-01-use-it-well.png"
944 alt="Section 6: Use it Well (1)" /></p>
945
946 </div><!-- /.sidebar -->
947 <div class="main">
948
949 <h3>When should I encrypt? When should I sign?</h3>
950
951 <p>The more you can encrypt your messages, the better. If you only encrypt
952 emails occasionally, each encrypted message could raise a red flag for
953 surveillance systems. If all or most of your email is encrypted, people
954 doing surveillance won't know where to start. That's not to say that only
955 encrypting some of your email isn't helpful -- it's a great start and it
956 makes bulk surveillance more difficult.</p>
957
958 <p>Unless you don't want to reveal your own identity (which requires other
959 protective measures), there's no reason not to sign every message, whether or
960 not you are encrypting. In addition to allowing those with GnuPG to verify
961 that the message came from you, signing is a non-intrusive way to remind
962 everyone that you use GnuPG and show support for secure communication. If you
963 often send signed messages to people that aren't familiar with GnuPG, it's
964 nice to also include a link to this guide in your standard email signature
965 (the text kind, not the cryptographic kind).</p>
966
967 </div><!-- End .main -->
968 </div><!-- End #step-6a .step -->
969
970 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
971 <div id="step-6b" class="step">
972 <div class="sidebar">
973
974 <p class="medium"><img
975 src="../static/img/en/screenshots/section6-02-use-it-well.png"
976 alt="Section 6: Use it Well (2)" /></p>
977
978 </div><!-- /.sidebar -->
979 <div class="main">
980
981 <h3>Be wary of invalid keys</h3>
982
983 <p>GnuPG makes email safer, but it's still important to watch out for invalid
984 keys, which might have fallen into the wrong hands. Email encrypted with
985 invalid keys might be readable by surveillance programs.</p>
986
987 <p>In your email program, go back to the first encrypted email that Edward
988 sent you. Because Edward encrypted it with your public key, it will have a
989 green checkmark a at the top "OpenPGP" button.</p>
990
991 <p><strong>When using GnuPG, make a habit of glancing at that button. The program
992 will warn you there if you get an email signed with a key that can't
993 be trusted.</strong></p>
994
995 </div><!-- End .main -->
996 </div><!-- End #step-6b .step -->
997
998 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
999 <div id="step-6c" class="step">
1000 <div class="main">
1001
1002 <h3>Copy your revocation certificate to somewhere safe</h3>
1003
1004 <p>Remember when you created your keys and saved the revocation certificate
1005 that GnuPG made? It's time to copy that certificate onto the safest storage that you have -- a flash drive, disk, or hard drive stored in a safe place in your home could work, not on a device you carry with you regularly. The safest way we know is actually to print the revocation certificate and store it in a safe place.</p>
1006
1007 <p>If your private key ever gets lost or stolen, you'll need this certificate
1008 file to let people know that you are no longer using that keypair.</p>
1009
1010 </div><!-- End .main -->
1011 </div><!-- End #step-6c .step -->
1012
1013 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1014 <div id="step-lost_key" class="step">
1015 <div class="main">
1016
1017 <h3><em>IMPORTANT:</em> ACT SWIFTLY if someone gets your private key</h3>
1018
1019 <p>If you lose your private key or someone else gets a hold
1020 of it (say, by stealing or cracking your computer), it's
1021 important to revoke it immediately before someone else uses
1022 it to read your encrypted email or forge your signature. This
1023 guide doesn't cover how to revoke a key, but you can follow these <a
1024 href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>.
1025 After you're done revoking, make a new key and send an email to everyone
1026 with whom you usually use your key to make sure they know, including a copy
1027 of your new key.</p>
1028
1029 </div><!-- End .main -->
1030 </div><!-- End #step-lost_key .step-->
1031
1032 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1033 <div id="webmail-and-GnuPG" class="step">
1034 <div class="main">
1035
1036 <h3>Webmail and GnuPG</h3>
1037
1038 <p>When you use a web browser to access your email, you're using webmail,
1039 an email program stored on a distant website. Unlike webmail, your desktop
1040 email program runs on your own computer. Although webmail can't decrypt
1041 encrypted email, it will still display it in its encrypted form. If you
1042 primarily use webmail, you'll know to open your email client when you receive
1043 a scrambled email.</p>
1044
1045 </div><!-- End .main -->
1046 </div><!-- End #webmail-and-GnuPG .step-->
1047
1048 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1049 <div id="step-6d" class="step">
1050 <div class="main">
1051
1052 <h3>Make your public key part of your online identity</h3>
1053
1054 <p> First add your public key fingerprint to your email signature, then
1055 compose an email to at least five of your friends, telling them you just
1056 set up GnuPG and mentioning your public key fingerprint. Link to this guide
1057 and ask them to join you. Don't forget that there's also an awesome <a
1058 href="infographic.html">infographic to share.</a></p>
1059
1060 <p class="notes">Start writing your public key fingerprint anywhere someone
1061 would see your email address: your social media profiles, blog, Website,
1062 or business card. (At the Free Software Foundation, we put ours on our
1063 <a href="https://fsf.org/about/staff">staff page</a>.) We need to get our
1064 culture to the point that we feel like something is missing when we see an
1065 email address without a public key fingerprint.</p>
1066
1067 </div><!-- End .main-->
1068 </div><!-- End #step-6d .step-->
1069 </div></section><!-- End #section6 -->
1070
1071 <!-- ~~~~~~~~~ Section 7: Next steps ~~~~~~~~~ -->
1072 <section class="row" id="section7">
1073 <div id="step-click_here" class="step">
1074 <div class="main">
1075
1076 <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>
1077
1078 </div><!-- End .main -->
1079 </div><!-- End #step-click_here .step-->
1080 </section><!-- End #section7 -->
1081
1082 <!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
1083 <!-- When un-commenting this section go to main.css and search
1084 for /* Guide Sections Background */ then add #faq to the desired color
1085 <section class="row" id="faq"><div>
1086 <div class="sidebar">
1087
1088 <h2>FAQ</h2>
1089
1090 </div>
1091 <div class="main">
1092
1093 <dl>
1094 <dt>My key expired</dt>
1095 <dd>Answer coming soon.</dd>
1096
1097 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
1098 <dd>Answer coming soon.</dd>
1099
1100 <dt>My email program is opening at times I don't want it to open/is now my
1101 default program and I don't want it to be.</dt>
1102 <dd>Answer coming soon.</dd>
1103 </dl>
1104
1105 </div>
1106 </div>
1107 </section> --><!-- End #faq -->
1108
1109 <!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
1110 <footer class="row" id="footer"><div>
1111 <div id="copyright">
1112
1113 <h4><a href="https://u.fsf.org/ys"><img
1114 alt="Free Software Foundation"
1115 src="../static/img/fsf-logo.png" /></a></h4>
1116
1117 <p>Copyright &copy; 2014-2021 <a
1118 href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a
1119 href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please
1120 support our work by <a href="https://u.fsf.org/yr">joining us as an associate
1121 member.</a></p>
1122
1123 <p>The images on this page are under a <a
1124 href="https://creativecommons.org/licenses/by/4.0/">Creative Commons
1125 Attribution 4.0 license (or later version)</a>, and the rest of it is under
1126 a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons
1127 Attribution-ShareAlike 4.0 license (or later version)</a>. Download the <a
1128 href="https://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
1129 source code of Edward reply bot</a> by Andrew Engelbrecht
1130 &lt;andrew@engelbrecht.io&gt; and Josh Drake &lt;zamnedix@gnu.org&gt;,
1131 available under the GNU Affero General Public License. <a
1132 href="https://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these
1133 licenses?</a></p>
1134
1135 <p>Fonts used in the guide &amp; infographic: <a
1136 href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo
1137 Impallari, <a href="https://www.google.com/fonts/specimen/Signika">Signika</a>
1138 by Anna Giedry&#347;, <a
1139 href="https://www.google.com/fonts/specimen/Archivo+Narrow">Archivo
1140 Narrow</a> by Omnibus-Type, <a
1141 href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a>
1142 by Florian Cramer.</p>
1143
1144 <p>Download the <a href="emailselfdefense_source.zip">source package</a>
1145 for this guide, including fonts, image source files and the text of Edward's
1146 messages.</p>
1147
1148 <p>This site uses the Weblabels standard for labeling <a
1149 href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View
1150 the JavaScript <a href="https://weblabels.fsf.org/emailselfdefense.fsf.org/"
1151 rel="jslicense">source code and license information</a>.</p>
1152
1153 </div><!-- /#copyright -->
1154
1155 <p class="credits">Infographic and guide design by <a rel="external"
1156 href="https://jplusplus.org"><strong>Journalism++</strong><img
1157 src="static/img/jplusplus.png"
1158 alt="Journalism++" /></a></p><!-- /.credits -->
1159 </div></footer><!-- End #footer -->
1160
1161
1162 <script type="text/javascript"
1163 src="../static/js/jquery-1.11.0.min.js"></script>
1164 <script type="text/javascript"
1165 src="../static/js/scripts.js"></script>
1166 <!-- Piwik -->
1167 <script type="text/javascript">
1168 // @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&amp;dn=gpl-2.0.txt GPL-2.0-or-later
1169 var _paq = _paq || [];
1170 _paq.push(["trackPageView"]);
1171 _paq.push(["enableLinkTracking"]);
1172
1173 (function() {
1174 var u = (("https:" == document.location.protocol) ? "https" : "http") + "://"+"piwik.fsf.org//";
1175 _paq.push(["setTrackerUrl", u+"piwik.php"]);
1176 _paq.push(["setSiteId", "13"]);
1177 var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
1178 g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
1179 })();
1180 // @license-end
1181 </script>
1182 <!-- End Piwik Code -->
1183 <!-- Piwik Image Tracker -->
1184 <noscript><img src="https://piwik.fsf.org//piwik.php?idsite=13&amp;rec=1" style="border:0" alt="" /></noscript>
1185 <!-- End Piwik -->
1186 </body>
1187 </html>