4 <meta http-equiv=
"content-type" content=
"text/html; charset=utf-8" />
5 <title>Email Self-Defense - a guide to fighting surveillance with GnuPG
7 <meta name=
"keywords" content=
"GnuPG, GPG, openpgp, surveillance, privacy,
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" />
20 <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
21 <header class=
"row" id=
"header"><div>
23 <h1>Email Self-Defense
</h1>
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>
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 class=
"spacer"><a href=
"workshops.html">Teach your friends
</a></li>
56 href=
"https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">
58 <img src=
"//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class=
"share-logo"
59 alt=
"[GNU Social]" />
60 <img src=
"//static.fsf.org/nosvn/enc-dev0/img/pump.io.png" class=
"share-logo"
61 alt=
"[Pump.io]" />
62 <img src=
"//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" class=
"share-logo"
63 alt=
"[Reddit]" />
64 <img src=
"//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" class=
"share-logo"
65 alt=
"[Hacker News]" /></a></li>
68 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
71 <h3><a href=
"http://u.fsf.org/ys"><img
72 alt=
"Free Software Foundation"
73 src=
"//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
76 <div class=
"fsf-emphasis">
78 <p>We fight for computer users' rights, and promote the development of free (as
79 in freedom) software. Resisting bulk surveillance is very important to us.
</p>
81 <p><strong>Please donate to support Email Self-Defense. We need to keep
82 improving it, and making more materials, for the benefit of people around
83 the world taking the first step towards protecting their privacy.
</strong></p>
88 href=
"https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img
90 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a></p>
92 </div><!-- End #fsf-intro -->
94 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
97 <p><a id=
"infographic" href=
"infographic.html"><img
98 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png"
99 alt=
"View & share our infographic →" /></a>
100 Bulk surveillance violates our fundamental rights and makes free speech
101 risky. This guide will teach you a basic surveillance self-defense skill: email
102 encryption. Once you've finished, you'll be able to send and receive emails
103 that are scrambled to make sure a surveillance agent or thief intercepting
104 your email can't read them. All you need is a computer with an Internet
105 connection, an email account, and about forty minutes.
</p>
107 <p>Even if you have nothing to hide, using encryption helps protect the privacy
108 of people you communicate with, and makes life difficult for bulk surveillance
109 systems. If you do have something important to hide, you're in good company;
110 these are the same tools that whistleblowers use to protect their identities
111 while shining light on human rights abuses, corruption and other crimes.
</p>
113 <p>In addition to using encryption, standing up
114 to surveillance requires fighting politically for a
<a
115 href=
"http://gnu.org/philosophy/surveillance-vs-democracy.html">reduction
116 in the amount of data collected on us
</a>, but the essential first step is
117 to protect yourself and make surveillance of your communication as difficult
118 as possible. This guide helps you do that. It is designed for beginners, but
119 if you already know the basics of GnuPG or are an experienced free software
120 user, you'll enjoy the advanced tips and the
<a href=
"workshops.html">guide
121 to teaching your friends
</a>.
</p>
123 </div><!-- End .intro -->
124 </div></header><!-- End #header -->
126 <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
127 <section class=
"row" id=
"section1"><div>
129 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
130 <div class=
"section-intro">
132 <h2><em>#
1</em> Get the pieces
</h2>
134 <p class=
"notes">This guide relies on software which is
<a
135 href=
"https://www.gnu.org/philosophy/free-sw.html">freely licensed
</a>; it's
136 completely transparent and anyone can copy it or make their own version. This
137 makes it safer from surveillance than proprietary software (like Windows or Mac
138 OS). To defend your freedom as well as protect yourself from surveillance, we
139 recommend you switch to a free software operating system like GNU/Linux. Learn
140 more about free software at
<a href=
"https://u.fsf.org/ys">fsf.org
</a>.
</p>
142 <p>To get started, you'll need the IceDove desktop email program installed
143 on your computer. For your system, IceDove may be known by the alternate name
144 "Thunderbird." Email programs are another way to access the same email accounts
145 you can access in a browser (like Gmail), but provide extra features.
</p>
147 <p>If you already have an email program, you can skip to
<a
148 href=
"#step-1b">Step
1.b
</a>.
</p>
150 </div><!-- End .section-intro -->
152 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
153 <div id=
"step-1a" class=
"step">
154 <div class=
"sidebar">
157 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png"
158 alt=
"Step 1.A: Install Wizard" /></p>
160 </div><!-- /.sidebar -->
163 <h3><em>Step
1.a
</em> Set up your email program with your email account
</h3>
165 <p>Open your email program and follow the wizard (step-by-step walkthrough)
166 that sets it up with your email account.
</p>
168 <p>Look for the letters SSL, TLS, or STARTTLS to the right of the servers
169 when you're setting up your account. If you don't see them, you will still
170 be able to use encryption, but this means that the people running your email
171 system are running behind the industry standard in protecting your security
172 and privacy. We recommend that you send them a friendly email asking them
173 to enable SSL, TLS, or STARTTLS for your email server. They will know what
174 you're talking about, so it's worth making the request even if you aren't
175 an expert on these security systems.
</p>
177 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
178 <div class=
"troubleshooting">
180 <h4>Troubleshooting
</h4>
183 <dt>The wizard doesn't launch
</dt>
184 <dd>You can launch the wizard yourself, but the menu option for doing so is
185 named differently in each email program. The button to launch it will be in
186 the program's main menu, under
"New" or something similar, titled something
187 like
"Add account" or
"New/Existing email account."</dd>
189 <dt>The wizard can't find my account or isn't downloading my mail
</dt>
190 <dd>Before searching the Web, we recommend you start by asking other people
191 who use your email system, to figure out the correct settings.
</dd>
193 <dt class=
"feedback">Don't see a solution to your problem?
</dt>
194 <dd class=
"feedback">Please let us know on the
<a
195 href=
"https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
199 </div><!-- /.troubleshooting -->
200 </div><!-- End .main -->
201 </div><!-- End #step1-a .step -->
203 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
204 <div id=
"step-1b" class=
"step">
207 <h3><em>Step
1.b
</em> Get GnuPG by downloading GPG4Win
</h3>
209 <p>GPG4Win is a software package that includes GnuPG.
<a
210 href=
"https://www.gpg4win.org/">Download
</a> and install it, choosing default
211 options whenever asked. After it's installed, you can close any windows that
214 <p>There are major security flaws in versions of GnuPG provided by GPG4Win
215 prior to
3.1.2. Make sure you have GPG4Win
3.1.2 or later.
</p>
217 </div><!-- End .main -->
218 </div><!-- End #step1-b .step -->
220 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
221 <div id=
"step-1c" class=
"step">
222 <div class=
"sidebar">
224 <li><img src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png"
225 alt=
"Step 1.C: Tools -> Add-ons" /></li>
226 <li><img src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png"
227 alt=
"Step 1.C: Search Add-ons" /></li>
228 <li><img src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png"
229 alt=
"Step 1.C: Install Add-ons" /></li>
232 </div><!-- /.sidebar -->
235 <h3><em>Step
1.c
</em> Install the Enigmail plugin for your email program
</h3>
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?
239 Make sure it's the latest version. If so, skip this step.
</p>
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>
244 <p>There are major security flaws in Enigmail prior to version
2.0.7. Make
245 sure you have Enigmail
2.0.7 or later.
</p>
247 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
248 <div class=
"troubleshooting">
250 <h4>Troubleshooting
</h4>
253 <dt>I can't find the menu.
</dt>
254 <dd>In many new email programs, the main menu is represented by an image of
255 three stacked horizontal bars.
</dd>
257 <dt>My email looks weird
</dt>
258 <dd>Enigmail doesn't tend to play nice with HTML, which is used to format
259 emails, so it may disable your HTML formatting automatically. To send an
260 HTML-formatted email without encryption or a signature, hold down the Shift
261 key when you select compose. You can then write an email as if Enigmail
264 <dt class=
"feedback">Don't see a solution to your problem?
</dt>
265 <dd class=
"feedback">Please let us know on the
<a
266 href=
"https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
270 </div><!-- /.troubleshooting -->
271 </div><!-- End .main -->
272 </div><!-- End #step-1b .step -->
273 </div></section><!-- End #section1 -->
275 <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
276 <section class=
"row" id=
"section2"><div>
278 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
279 <div class=
"section-intro">
281 <h2><em>#
2</em> Make your keys
</h2>
283 <p>To use the GnuPG system, you'll need a public key and a private key (known
284 together as a keypair). Each is a long string of randomly generated numbers
285 and letters that are unique to you. Your public and private keys are linked
286 together by a special mathematical function.
</p>
288 <p>Your public key isn't like a physical key, because it's stored in the open
289 in an online directory called a keyserver. People download it and use it,
290 along with GnuPG, to encrypt emails they send to you. You can think of the
291 keyserver as a phonebook; people who want to send you encrypted email can
292 look up your public key.
</p>
294 <p>Your private key is more like a physical key, because you keep it to
295 yourself (on your computer). You use GnuPG and your private key together to
296 descramble encrypted emails other people send to you.
<span style=
"font-weight:
297 bold;">You should never share you private key with anyone, under any
298 circumstances.
</span></p>
300 <p>In addition to encryption and decryption, you can also use these keys to
301 sign messages and check the authenticity of other people's signatures. We'll
302 discuss this more in the next section.
</p>
304 </div><!-- End .section-intro -->
306 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
307 <div id=
"step-2a" class=
"step">
308 <div class=
"sidebar">
311 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png"
312 alt=
"Step 2.A: Make a Keypair" /></p>
314 </div><!-- /.sidebar -->
317 <h3><em>Step
2.a
</em> Make a keypair
</h3>
319 <p>The Enigmail Setup wizard may start automatically. If it doesn't, select
320 Enigmail
→ Setup Wizard from your email program's menu. You don't need
321 to read the text in the window that pops up unless you'd like to, but it's
322 good to read the text on the later screens of the wizard. Click Next with
323 the default options selected, except in these instances, which are listed
324 in the order they appear:
</p>
327 <li>On the screen titled
"Encryption," select
"Encrypt all of my messages
328 by default, because privacy is critical to me."</li>
330 <li>On the screen titled
"Signing," select
"Don't sign my messages by
333 <li>On the screen titled
"Key Selection," select
"I want to create a new
334 key pair for signing and encrypting my email."</li>
336 <li>On the screen titled
"Create Key," pick a strong password! You can
337 do it manually, or you can use the Diceware method. Doing it manually
338 is faster but not as secure. Using Diceware takes longer and requires
339 dice, but creates a password that is much harder for attackers figure
340 out. To use it, read the section
"Make a secure passphrase with Diceware" in
<a
341 href=
"https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">
342 this article
</a> by Micah Lee.
</li>
345 <p>If you'd like to pick a password manually, come up with something
346 you can remember which is at least twelve characters long, and includes
347 at least one lower case and upper case letter and at least one number or
348 punctuation symbol. Never pick a password you've used elsewhere. Don't use
349 any recognizable patterns, such as birthdays, telephone numbers, pets' names,
350 song lyrics, quotes from books, and so on.
</p>
352 <p class=
"notes">The program will take a little while to finish the next
353 step, the
"Key Creation" screen. While you wait, do something else with your
354 computer, like watching a movie or browsing the Web. The more you use the
355 computer at this point, the faster the key creation will go.
</p>
357 <p><span style=
"font-weight: bold;">When the
"Key Generation Completed" screen
358 pops up, select Generate Certificate and choose to save it in a safe place on
359 your computer (we recommend making a folder called
"Revocation Certificate"
360 in your home folder and keeping it there). This step is essential for your
361 email self-defense, as you'll learn more about in
<a href=
"#section5">Section
364 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
365 <div class=
"troubleshooting">
367 <h4>Troubleshooting
</h4>
370 <dt>I can't find the Enigmail menu.
</dt>
371 <dd>In many new email programs, the main menu is represented by an image
372 of three stacked horizontal bars. Enigmail may be inside a section called
375 <dt>The wizard says that it cannot find GnuPG.
</dt>
376 <dd>Open whatever program you usually use for installing software, and search
377 for GnuPG, then install it. Then restart the Enigmail setup wizard by going
378 to Enigmail
→ Setup Wizard.
</dd>
380 <dt>My email looks weird
</dt>
381 <dd>Enigmail doesn't tend to play nice with HTML, which is used to format
382 emails, so it may disable your HTML formatting automatically. To send an
383 HTML-formatted email without encryption or a signature, hold down the Shift
384 key when you select compose. You can then write an email as if Enigmail
387 <dt>More resources
</dt>
388 <dd>If you're having trouble with our
389 instructions or just want to learn more, check out
<a
390 href=
"https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">
391 Enigmail's wiki instructions for key generation
</a>.
</dd>
393 <dt class=
"feedback">Don't see a solution to your problem?
</dt>
394 <dd class=
"feedback">Please let us know on the
<a
395 href=
"https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
399 </div><!-- /.troubleshooting -->
401 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
402 <div class=
"troubleshooting">
407 <dt>Command line key generation
</dt>
408 <dd>If you prefer using the command line for a higher
409 degree of control, you can follow the documentation from
<a
410 href=
"https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy
411 Handbook
</a>. Make sure you stick with
"RSA and RSA" (the default),
412 because it's newer and more secure than the algorithms the documentation
413 recommends. Also make sure your key is at least
2048 bits, or
4096 if you
414 want to be extra secure.
</dd>
416 <dt>Advanced key pairs
</dt>
417 <dd>When GnuPG creates a new keypair, it compartmentalizes
418 the encryption function from the signing function through
<a
419 href=
"https://wiki.debian.org/Subkeys">subkeys
</a>. If you use
420 subkeys carefully, you can keep your GnuPG identity much more
421 secure and recover from a compromised key much more quickly.
<a
422 href=
"https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal
</a>
423 and
<a href=
"http://keyring.debian.org/creating-key.html">the Debian wiki
</a>
424 provide good guides for setting up a secure subkey configuration.
</dd>
427 </div><!-- /.troubleshooting -->
428 </div><!-- End .main -->
429 </div><!-- End #step-2a .step -->
431 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
432 <div id=
"step-2b" class=
"step">
435 <h3><em>Step
2.b
</em> Upload your public key to a keyserver
</h3>
437 <p>In your email program's menu, select Enigmail
→ Key Management.
</p>
439 <p>Right click on your key and select Upload Public Keys to Keyserver. Use
440 the default keyserver in the popup.
</p>
442 <p class=
"notes">Now someone who wants to send you an encrypted message can
443 download your public key from the Internet. There are multiple keyservers
444 that you can select from the menu when you upload, but they are all copies
445 of each other, so it doesn't matter which one you use. However, it sometimes
446 takes a few hours for them to match each other when a new key is uploaded.
</p>
448 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
449 <div class=
"troubleshooting">
451 <h4>Troubleshooting
</h4>
454 <dt>The progress bar never finishes
</dt>
455 <dd>Close the upload popup, make sure you are connected to the Internet,
456 and try again. If that doesn't work, try again, selecting a different
459 <dt>My key doesn't appear in the list
</dt>
460 <dd>Try checking
"Display All Keys by Default."</dd>
462 <dt>More documentation
</dt>
463 <dd>If you're having trouble with our
464 instructions or just want to learn more, check out
<a
465 href=
"https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">
466 Enigmail's documentation
</a>.
</dd>
468 <dt class=
"feedback">Don't see a solution to your problem?
</dt>
469 <dd class=
"feedback">Please let us know on the
<a
470 href=
"https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
474 </div><!-- /.troubleshooting -->
476 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
477 <div class=
"troubleshooting">
482 <dt>Uploading a key from the command line
</dt>
483 <dd>You can also upload your keys to a keyserver through the
<a
484 href=
"https://www.gnupg.org/gph/en/manual/x457.html">command line
</a>.
<a
485 href=
"https://sks-keyservers.net/overview-of-pools.php">The sks Web site
</a>
486 maintains a list of highly interconnected keyservers. You can also
<a
487 href=
"https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export
488 your key
</a> as a file on your computer.
</dd>
491 </div><!-- /.troubleshooting -->
492 </div><!-- End .main -->
493 </div><!-- End #step-2b .step -->
495 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
496 <div id=
"terminology" class=
"step">
499 <h3>GnuPG, OpenPGP, what?
</h3>
501 <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP
502 are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the
503 encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG)
504 is the program that implements the standard. Enigmail is a plug-in program
505 for your email program that provides an interface for GnuPG.
</p>
507 </div><!-- End .main -->
508 </div><!-- End #terminology.step-->
509 </div></section><!-- End #section2 -->
511 <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
512 <section class=
"row" id=
"section3"><div>
514 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
515 <div class=
"section-intro">
517 <h2><em>#
3</em> Try it out!
</h2>
519 <p>Now you'll try a test correspondence with a computer program named Edward,
520 who knows how to use encryption. Except where noted, these are the same
521 steps you'd follow when corresponding with a real, live person.
</p>
523 <!-- <p>NOTE: Edward is currently having some technical difficulties, so he
524 may take a long time to respond, or not respond at all. We're sorry about
525 this and we're working hard to fix it. Your key will still work even without
526 testing with Edward.</p> -->
527 </div><!-- End .section-intro -->
529 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
530 <div id=
"step-3a" class=
"step">
531 <div class=
"sidebar">
534 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png"
535 alt=
"Try it out." /></p>
537 </div><!-- /.sidebar -->
540 <h3><em>Step
3.a
</em> Send Edward your public key
</h3>
542 <p>This is a special step that you won't have to do when corresponding
543 with real people. In your email program's menu, go to Enigmail
→ Key
544 Management. You should see your key in the list that pops up. Right click
545 on your key and select Send Public Keys by Email. This will create a new
546 draft message, as if you had just hit the Write button.
</p>
548 <p>Address the message to
<a
549 href=
"mailto:edward-en@fsf.org">edward-en@fsf.org
</a>. Put at least one word
550 (whatever you want) in the subject and body of the email. Don't send yet.
</p>
552 <p>The lock icon in the top left should be yellow, meaning encryption is
553 turned on. We want this first special message to be unencrypted, so
554 click the icon once to turn it off. The lock should become grey, with a
555 blue dot on it (to alert you that the setting has been changed from the
556 default). Once encryption is off, hit Send.
</p>
558 <p class=
"notes">It may take two or three minutes for Edward to
559 respond. In the meantime, you might want to skip ahead and check out the
<a
560 href=
"#section5">Use it Well
</a> section of this guide. Once he's responded,
561 head to the next step. From here on, you'll be doing just the same thing as
562 when corresponding with a real person.
</p>
564 <p>When you open Edward's reply, GnuPG may prompt you for your password
565 before using your private key to decrypt it.
</p>
567 </div><!-- End .main -->
568 </div><!-- End #step-3a .step -->
570 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
571 <div id=
"step-3b" class=
"step">
574 <h3><em>Step
3.b
</em> Send a test encrypted email
</h3>
576 <p>Write a new email in your email program, addressed to
<a
577 href=
"mailto:edward-en@fsf.org">edward-en@fsf.org
</a>. Make the subject
578 "Encryption test" or something similar and write something in the body.
</p>
580 <p>The lock icon in the top left of the window should be yellow, meaning
581 encryption is on. This will be your default from now on.
</p>
583 <p class=
"notes">Next to the lock, you'll notice an icon of a pencil. We'll
584 get to this in a moment.
</p>
586 <p>Click Send. Enigmail will pop up a window that says
"Recipients not valid,
587 not trusted or not found."</p>
589 <p>To encrypt an email to Edward, you need his public key, so now you'll have
590 Enigmail download it from a keyserver. Click Download Missing Keys and use
591 the default in the pop-up that asks you to choose a keyserver. Once it finds
592 keys, check the first one (Key ID starting with C), then select ok. Select
593 ok in the next pop-up.
</p>
595 <p>Now you are back at the
"Recipients not valid, not trusted or not found"
596 screen. Check the box in front of Edward's key and click Send.
</p>
598 <p class=
"notes">Since you encrypted this email with Edward's public key,
599 Edward's private key is required to decrypt it. Edward is the only one with
600 his private key, so no one except him can decrypt it.
</p>
602 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
603 <div class=
"troubleshooting">
605 <h4>Troubleshooting
</h4>
608 <dt>Enigmail can't find Edward's key
</dt>
609 <dd>Close the pop-ups that have appeared since you clicked Send. Make sure
610 you are connected to the Internet and try again. If that doesn't work, repeat
611 the process, choosing a different keyserver when it asks you to pick one.
</dd>
613 <dt>Unscrambled messages in the Sent folder
</dt>
614 <dd>Even though you can't decrypt messages encrypted to someone else's key,
615 your email program will automatically save a copy encrypted to your public key,
616 which you'll be able to view from the Sent folder like a normal email. This
617 is normal, and it doesn't mean that your email was not sent encrypted.
</dd>
619 <dt>More resources
</dt>
620 <dd>If you're still having trouble with our
621 instructions or just want to learn more, check out
<a
622 href=
"https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">
623 Enigmail's wiki
</a>.
</dd>
625 <dt class=
"feedback">Don't see a solution to your problem?
</dt>
626 <dd class=
"feedback">Please let us know on the
<a
627 href=
"https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
631 </div><!-- /.troubleshooting -->
633 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
634 <div class=
"troubleshooting">
639 <dt>Encrypt messages from the command line
</dt>
640 <dd>You can also encrypt and decrypt messages and files from the
<a
641 href=
"https://www.gnupg.org/gph/en/manual/x110.html">command line
</a>,
642 if that's your preference. The option --armor makes the encrypted output
643 appear in the regular character set.
</dd>
646 </div><!-- /.troubleshooting -->
647 </div><!-- End .main -->
648 </div><!-- End #step-3b .step -->
650 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
651 <div id=
"step-headers_unencrypted" class=
"step">
654 <h3><em>Important:
</em> Security tips
</h3>
656 <p>Even if you encrypt your email, the subject line is not encrypted, so
657 don't put private information there. The sending and receiving addresses
658 aren't encrypted either, so a surveillance system can still figure out who
659 you're communicating with. Also, surveillance agents will know that you're
660 using GnuPG, even if they can't figure out what you're saying. When you
661 send attachments, Enigmail will give you the choice to encrypt them or not,
662 independent of the actual email.
</p>
664 <p>For greater security against potential attacks, you can turn off
665 HTML. Instead, you can render the message body as plain text.
</p>
667 </div><!-- End .main -->
668 </div><!-- End #step-headers_unencrypted .step-->
670 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
671 <div id=
"step-3c" class=
"step">
674 <h3><em>Step
3.c
</em> Receive a response
</h3>
676 <p>When Edward receives your email, he will use his private key to decrypt
677 it, then use your public key (which you sent him in
<a href=
"#step-3a">Step
678 3.A
</a>) to encrypt his reply to you.
</p>
680 <p class=
"notes">It may take two or three minutes for Edward to
681 respond. In the meantime, you might want to skip ahead and check out the
<a
682 href=
"#section5">Use it Well
</a> section of this guide.
</p>
684 <p>When you receive Edward's email and open it, Enigmail will automatically
685 detect that it is encrypted with your public key, and then it will use your
686 private key to decrypt it.
</p>
688 <p>Notice the bar that Enigmail shows you above the message, with information
689 about the status of Edward's key.
</p>
691 </div><!-- End .main -->
692 </div><!-- End #step-3c .step -->
694 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
695 <div id=
"step-3d" class=
"step">
698 <h3><em>Step
3.d
</em> Send a test signed email
</h3>
700 <p>GnuPG includes a way for you to sign messages and files, verifying that
701 they came from you and that they weren't tampered with along the way. These
702 signatures are stronger than their pen-and-paper cousins -- they're impossible
703 to forge, because they're impossible to create without your private key
704 (another reason to keep your private key safe).
</p>
706 <p>You can sign messages to anyone, so it's a great way to make people
707 aware that you use GnuPG and that they can communicate with you securely. If
708 they don't have GnuPG, they will be able to read your message and see your
709 signature. If they do have GnuPG, they'll also be able to verify that your
710 signature is authentic.
</p>
712 <p>To sign an email to Edward, compose any message to him and click the
713 pencil icon next to the lock icon so that it turns gold. If you sign a
714 message, GnuPG may ask you for your password before it sends the message,
715 because it needs to unlock your private key for signing.
</p>
717 <p>With the lock and pencil icons, you can choose whether each message will
718 be encrypted, signed, both, or neither.
</p>
723 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
724 <div id=
"step-3e" class=
"step">
727 <h3><em>Step
3.e
</em> Receive a response
</h3>
729 <p>When Edward receives your email, he will use your public key (which you
730 sent him in
<a href=
"#step-3a">Step
3.A
</a>) to verify that your signature
731 is authentic and the message you sent has not been tampered with.
</p>
733 <p class=
"notes">It may take two or three minutes for Edward to
734 respond. In the meantime, you might want to skip ahead and check out the
<a
735 href=
"#section5">Use it Well
</a> section of this guide.
</p>
737 <p>Edward's reply will arrive encrypted, because he prefers to use encryption
738 whenever possible. If everything goes according to plan, it should say
739 "Your signature was verified." If your test signed email was also encrypted,
740 he will mention that first.
</p>
742 </div><!-- End .main -->
743 </div><!-- End #step-3e .step -->
746 <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
747 <section class=
"row" id=
"section4"><div>
749 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
750 <div class=
"section-intro">
752 <h2><em>#
4</em> Learn the Web of Trust
</h2>
754 <p>Email encryption is a powerful technology, but it has a weakness;
755 it requires a way to verify that a person's public key is actually
756 theirs. Otherwise, there would be no way to stop an attacker from making
757 an email address with your friend's name, creating keys to go with it and
758 impersonating your friend. That's why the free software programmers that
759 developed email encryption created keysigning and the Web of Trust.
</p>
761 <p>When you sign someone's key, you are publicly saying that you've verified
762 that it belongs to them and not someone else.
</p>
764 <p>Signing keys and signing messages use the same type of mathematical
765 operation, but they carry very different implications. It's a good practice
766 to generally sign your email, but if you casually sign people's keys, you
767 may accidently end up vouching for the identity of an imposter.
</p>
769 <p>People who use your public key can see who has signed it. Once you've
770 used GnuPG for a long time, your key may have hundreds of signatures. You
771 can consider a key to be more trustworthy if it has many signatures from
772 people that you trust. The Web of Trust is a constellation of GnuPG users,
773 connected to each other by chains of trust expressed through signatures.
</p>
775 </div><!-- End .section-intro -->
777 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
778 <div id=
"step-4a" class=
"step">
779 <div class=
"sidebar">
782 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png"
783 alt=
"Section 4: Web of Trust" /></p>
785 </div><!-- /.sidebar -->
788 <h3><em>Step
4.a
</em> Sign a key
</h3>
790 <p>In your email program's menu, go to Enigmail
→ Key Management.
</p>
792 <p>Right click on Edward's public key and select Sign Key from the context
795 <p>In the window that pops up, select
"I will not answer" and click ok.
</p>
797 <p>Now you should be back at the Key Management menu. Select Keyserver
→
798 Upload Public Keys and hit ok.
</p>
800 <p class=
"notes">You've just effectively said
"I trust that Edward's public
801 key actually belongs to Edward." This doesn't mean much because Edward isn't
802 a real person, but it's good practice.
</p>
804 <!--<div id="pgp-pathfinder">
806 <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi"
809 <p><strong>From:</strong><input type="text" value="xD41A008"
812 <p><strong>To:</strong><input type="text" value="50BD01x4" name="TO"></p>
814 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"><input
815 type="reset" value="reset" name=".reset"></p>
819 </div>End #pgp-pathfinder -->
820 </div><!-- End .main -->
821 </div><!-- End #step-4a .step -->
823 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
824 <div id=
"step-identify_keys" class=
"step">
827 <h3>Identifying keys: Fingerprints and IDs
</h3>
829 <p>People's public keys are usually identified by their key fingerprint,
830 which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8
831 (for Edward's key). You can see the fingerprint for your public key, and
832 other public keys saved on your computer, by going to Enigmail
→ Key
833 Management in your email program's menu, then right clicking on the key
834 and choosing Key Properties. It's good practice to share your fingerprint
835 wherever you share your email address, so that people can double-check that
836 they have the correct public key when they download yours from a keyserver.
</p>
838 <p class=
"notes">You may also see public keys referred to by a shorter
839 key ID. This key ID is visible directly from the Key Management
840 window. These eight character key IDs were previously used for
841 identification, which used to be safe, but is no longer reliable. You
842 need to check the full fingerprint as part of verifying you have the
843 correct key for the person you are trying to contact. Spoofing, in
844 which someone intentionally generates a key with a fingerprint whose
845 final eight characters are the same as another, is unfortunately
848 </div><!-- End .main -->
849 </div><!-- End #step-identify_keys .step-->
851 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
852 <div id=
"check-ids-before-signing" class=
"step">
855 <h3><em>Important:
</em> What to consider when signing keys
</h3>
857 <p>Before signing a person's key, you need to be confident that it actually
858 belongs to them, and that they are who they say they are. Ideally, this
859 confidence comes from having interactions and conversations with them over
860 time, and witnessing interactions between them and others. Whenever signing
861 a key, ask to see the full public key fingerprint, and not just the shorter
862 key ID. If you feel it's important to sign the key of someone you've just
863 met, also ask them to show you their government identification, and make
864 sure the name on the ID matches the name on the public key. In Enigmail,
865 answer honestly in the window that pops up and asks
"How carefully have you
866 verified that the key you are about to sign actually belongs to the person(s)
869 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
870 <div class=
"troubleshooting">
875 <dt>Master the Web of Trust
</dt>
876 <dd>Unfortunately, trust does not spread between users the way
<a
877 href=
"http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people
878 think
</a>. One of best ways to strengthen the GnuPG community is to deeply
<a
879 href=
"https://www.gnupg.org/gph/en/manual/x334.html">understand
</a> the Web of
880 Trust and to carefully sign as many people's keys as circumstances permit.
</dd>
882 <dt>Set ownertrust
</dt>
883 <dd>If you trust someone enough to validate other people's keys, you can assign
884 them an ownertrust level through Enigmails's key management window. Right
885 click on the other person's key, go to the
"Select Owner Trust" menu option,
886 select the trustlevel and click OK. Only do this once you feel you have a
887 deep understanding of the Web of Trust.
</dd>
890 </div><!-- /.troubleshooting -->
891 </div><!-- End .main -->
892 </div><!-- End #check-ids-before-signing .step-->
893 </div></section><!-- End #section4 -->
895 <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
896 <section id=
"section5" class=
"row"><div>
898 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
899 <div class=
"section-intro">
901 <h2><em>#
5</em> Use it well
</h2>
903 <p>Everyone uses GnuPG a little differently, but it's important to follow
904 some basic practices to keep your email secure. Not following them, you
905 risk the privacy of the people you communicate with, as well as your own,
906 and damage the Web of Trust.
</p>
908 </div><!-- End .section-intro -->
910 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
911 <div id=
"step-5a" class=
"step">
912 <div class=
"sidebar">
915 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png"
916 alt=
"Section 5: Use it Well (1)" /></p>
918 </div><!-- /.sidebar -->
921 <h3>When should I encrypt? When should I sign?
</h3>
923 <p>The more you can encrypt your messages, the better. If you only encrypt
924 emails occasionally, each encrypted message could raise a red flag for
925 surveillance systems. If all or most of your email is encrypted, people
926 doing surveillance won't know where to start. That's not to say that only
927 encrypting some of your email isn't helpful -- it's a great start and it
928 makes bulk surveillance more difficult.
</p>
930 <p>Unless you don't want to reveal your own identity (which requires other
931 protective measures), there's no reason not to sign every message, whether or
932 not you are encrypting. In addition to allowing those with GnuPG to verify
933 that the message came from you, signing is a non-intrusive way to remind
934 everyone that you use GnuPG and show support for secure communication. If you
935 often send signed messages to people that aren't familiar with GnuPG, it's
936 nice to also include a link to this guide in your standard email signature
937 (the text kind, not the cryptographic kind).
</p>
939 </div><!-- End .main -->
940 </div><!-- End #step-5a .step -->
942 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
943 <div id=
"step-5b" class=
"step">
944 <div class=
"sidebar">
947 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png"
948 alt=
"Section 5: Use it Well (2)" /></p>
950 </div><!-- /.sidebar -->
953 <h3>Be wary of invalid keys
</h3>
955 <p>GnuPG makes email safer, but it's still important to watch out for invalid
956 keys, which might have fallen into the wrong hands. Email encrypted with
957 invalid keys might be readable by surveillance programs.
</p>
959 <p>In your email program, go back to the first encrypted email that Edward
960 sent you. Because Edward encrypted it with your public key, it will have a
961 message from Enigmail at the top, which most likely says
"Enigmail: Part of
962 this message encrypted."</p>
964 <p><b>When using GnuPG, make a habit of glancing at that bar. The program
965 will warn you there if you get an email signed with a key that can't
968 </div><!-- End .main -->
969 </div><!-- End #step-5b .step -->
971 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
972 <div id=
"step-5c" class=
"step">
975 <h3>Copy your revocation certificate to somewhere safe
</h3>
977 <p>Remember when you created your keys and saved the revocation certificate
978 that GnuPG made? It's time to copy that certificate onto the safest digital
979 storage that you have -- the ideal thing is a flash drive, disk, or hard
980 drive stored in a safe place in your home, not on a device you carry with
983 <p>If your private key ever gets lost or stolen, you'll need this certificate
984 file to let people know that you are no longer using that keypair.
</p>
986 </div><!-- End .main -->
987 </div><!-- End #step-5c .step -->
989 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
990 <div id=
"step-lost_key" class=
"step">
993 <h3><em>Important:
</em> act swiftly if someone gets your private key
</h3>
995 <p>If you lose your private key or someone else gets ahold
996 of it (say, by stealing or cracking your computer), it's
997 important to revoke it immediately before someone else uses
998 it to read your encrypted email or forge your signature. This
999 guide doesn't cover how to revoke a key, but you can follow these
<a
1000 href=
"https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions
</a>.
1001 After you're done revoking, make a new key and send an email to everyone
1002 with whom you usually use your key to make sure they know, including a copy
1003 of your new key.
</p>
1005 </div><!-- End .main -->
1006 </div><!-- End #step-lost_key .step-->
1008 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1009 <!---<div id="transfer-key" class="step">
1012 <h3>Transferring you key</h3>
1014 <p>You can use Enigmail's <a
1015 href="https://www.enigmail.net/documentation/keyman.php">key management
1016 window</a> to import and export keys. If you want to be able to read
1017 your encrypted email on a different computer, you will need to export
1018 your secret key from here. Be warned, if you transfer the key without <a
1019 href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a>
1020 the drive it's on the transfer will be dramatically less secure.</p>
1022 </div>--><!-- End .main
1023 </div> End #transfer-key .step-->
1025 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1026 <div id=
"webmail-and-GnuPG" class=
"step">
1029 <h3>Webmail and GnuPG
</h3>
1031 <p>When you use a web browser to access your email, you're using webmail,
1032 an email program stored on a distant website. Unlike webmail, your desktop
1033 email program runs on your own computer. Although webmail can't decrypt
1034 encrypted email, it will still display it in its encrypted form. If you
1035 primarily use webmail, you'll know to open your email client when you receive
1036 a scrambled email.
</p>
1038 </div><!-- End .main -->
1039 </div><!-- End #webmail-and-GnuPG .step-->
1041 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
1042 <div id="step-5d" class="step">
1045 <h3>Make your public key part of your online identity</h3>
1047 <p> First add your public key fingerprint to your email signature, then
1048 compose an email to at least five of your friends, telling them you just
1049 set up GnuPG and mentioning your public key fingerprint. Link to this guide
1050 and ask them to join you. Don't forget that there's also an awesome <a
1051 href="infographic.html">infographic to share.</a></p>
1053 <p class="notes">Start writing your public key fingerprint anywhere someone
1054 would see your email address: your social media profiles, blog, Website,
1055 or business card. (At the Free Software Foundation, we put ours on our
1056 <a href="https://fsf.org/about/staff">staff page</a>.) We need to get our
1057 culture to the point that we feel like something is missing when we see an
1058 email address without a public key fingerprint.</p>
1060 </div>--><!-- End .main
1061 </div> End #step-5d .step-->
1062 </div></section><!-- End #section5 -->
1064 <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
1065 <section class=
"row" id=
"section6">
1066 <div id=
"step-click_here" class=
"step">
1069 <h2><a href=
"next_steps.html">Great job! Check out the next steps.
</a></h2>
1071 </div><!-- End .main -->
1072 </div><!-- End #step-click_here .step-->
1073 </section><!-- End #section6 -->
1075 <!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
1076 <!-- When un-commenting this section go to main.css and search
1077 for /* Guide Sections Background */ then add #faq to the desired color
1078 <section class="row" id="faq"><div>
1079 <div class="sidebar">
1087 <dt>My key expired</dt>
1088 <dd>Answer coming soon.</dd>
1090 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
1091 <dd>Answer coming soon.</dd>
1093 <dt>My email program is opening at times I don't want it to open/is now my
1094 default program and I don't want it to be.</dt>
1095 <dd>Answer coming soon.</dd>
1100 </section> --><!-- End #faq -->
1102 <!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
1103 <footer class=
"row" id=
"footer"><div>
1104 <div id=
"copyright">
1106 <h4><a href=
"https://u.fsf.org/ys"><img
1107 alt=
"Free Software Foundation"
1108 src=
"//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" /></a></h4>
1110 <p>Copyright
© 2014-
2016 <a
1111 href=
"https://u.fsf.org/ys">Free Software Foundation
</a>, Inc.
<a
1112 href=
"https://my.fsf.org/donate/privacypolicy.html">Privacy Policy
</a>. Please
1113 support our work by
<a href=
"https://u.fsf.org/yr">joining us as an associate
1116 <p>The images on this page are under a
<a
1117 href=
"https://creativecommons.org/licenses/by/4.0/">Creative Commons
1118 Attribution
4.0 license (or later version)
</a>, and the rest of it is under
1119 a
<a href=
"https://creativecommons.org/licenses/by-sa/4.0">Creative Commons
1120 Attribution-ShareAlike
4.0 license (or later version)
</a>. Download the
<a
1121 href=
"http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
1122 source code of Edward reply bot
</a> by Andrew Engelbrecht
1123 <sudoman@ninthfloor.org
> and Josh Drake
<zamnedix@gnu.org
>,
1124 available under the GNU Affero General Public License.
<a
1125 href=
"http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these
1128 <p>Fonts used in the guide
& infographic:
<a
1129 href=
"https://www.google.com/fonts/specimen/Dosis">Dosis
</a> by Pablo
1130 Impallari,
<a href=
"http://www.google.com/fonts/specimen/Signika">Signika
</a>
1131 by Anna Giedry
ś,
<a
1132 href=
"http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo
1133 Narrow
</a> by Omnibus-Type,
<a
1134 href=
"https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-
2000</a>
1135 by Florian Cramer.
</p>
1137 <p>Download the
<a href=
"emailselfdefense_source.zip">source package
</a>
1138 for this guide, including fonts, image source files and the text of Edward's
1141 <p>This site uses the Weblabels standard for labeling
<a
1142 href=
"https://www.fsf.org/campaigns/freejs">free JavaScript
</a>. View
1143 the JavaScript
<a href=
"//weblabels.fsf.org/emailselfdefense.fsf.org/"
1144 rel=
"jslicense">source code and license information
</a>.
</p>
1146 </div><!-- /#copyright -->
1148 <p class=
"credits">Infographic and guide design by
<a rel=
"external"
1149 href=
"http://jplusplus.org"><strong>Journalism++
</strong><img
1150 src=
"//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png"
1151 alt=
"Journalism++" /></a></p><!-- /.credits -->
1152 </div></footer><!-- End #footer -->
1155 <script type=
"text/javascript"
1156 src=
"//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
1157 <script type=
"text/javascript"
1158 src=
"//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
1160 <script type=
"text/javascript" ><!--
1161 // @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
1162 var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");
1163 document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
1165 var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);
1166 piwikTracker.trackPageView();
1167 piwikTracker.enableLinkTracking();
1172 src=
"//piwik.fsf.org/piwik.php?idsite=13" style=
"border:0"
1173 alt=
"" /></p></noscript>
1174 <!-- End Piwik Tracking Code -->