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