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=
"/cs">čeština - v4.0
</a></li>
29 <li><a href=
"/de">Deutsch - v4.0
</a></li>
30 <li><a href=
"/el">ελληνικά - v3.0
</a></li>
31 <li><a href=
"/es">español - v4.0
</a></li>
32 <li><a href=
"/fa">فارسی - v4.0
</a></li>
33 <li><a href=
"/fr">français - v4.0
</a></li>
34 <li><a href=
"/it">italiano - v3.0
</a></li>
35 <li><a href=
"/ja">日本語 - v4.0
</a></li>
36 <li><a href=
"/pt-br">português do Brasil - v3.0
</a></li>
37 <li><a href=
"/ro">română - v3.0
</a></li>
38 <li><a href=
"/ru">русский - v4.0
</a></li>
39 <li><a href=
"/sq">Shqip - v4.0
</a></li>
40 <li><a href=
"/sv">svenska - v4.0
</a></li>
41 <li><a href=
"/tr">Türkçe - v4.0
</a></li>
42 <li><a href=
"/zh-hans">简体中文 - v4.0
</a></li>
43 <li><a href=
"https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
44 <strong><span style=
"color: #2F5FAA;">Translate!
</span></strong></a></li>
47 <ul id=
"menu" class=
"os">
48 <li class=
"spacer"><a href=
"index.html">GNU/Linux
</a></li>
49 <li><a href=
"mac.html" class=
"current">Mac OS
</a></li>
50 <li><a href=
"windows.html">Windows
</a></li>
51 <li class=
"spacer"><a href=
"workshops.html">Teach your friends
</a></li>
53 href=
"https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">
55 <img src=
"//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class=
"share-logo"
56 alt=
"[GNU Social]" />
57 <img src=
"//static.fsf.org/nosvn/enc-dev0/img/pump.io.png" class=
"share-logo"
58 alt=
"[Pump.io]" />
59 <img src=
"//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" class=
"share-logo"
60 alt=
"[Reddit]" />
61 <img src=
"//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" class=
"share-logo"
62 alt=
"[Hacker News]" /></a></li>
65 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
68 <h3><a href=
"http://u.fsf.org/ys"><img
69 alt=
"Free Software Foundation"
70 src=
"//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
73 <div class=
"fsf-emphasis">
75 <p>We fight for computer users' rights, and promote the development of free (as
76 in freedom) software. Resisting bulk surveillance is very important to us.
</p>
78 <p><strong>Please donate to support Email Self-Defense. We need to keep
79 improving it, and making more materials, for the benefit of people around
80 the world taking the first step towards protecting their privacy.
</strong></p>
85 href=
"https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img
87 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a></p>
89 </div><!-- End #fsf-intro -->
91 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
94 <p><a id=
"infographic" href=
"infographic.html"><img
95 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png"
96 alt=
"View & share our infographic →" /></a>
97 Bulk surveillance violates our fundamental rights and makes free speech
98 risky. This guide will teach you a basic surveillance self-defense skill: email
99 encryption. Once you've finished, you'll be able to send and receive emails
100 that are scrambled to make sure a surveillance agent or thief intercepting
101 your email can't read them. All you need is a computer with an Internet
102 connection, an email account, and about forty minutes.
</p>
104 <p>Even if you have nothing to hide, using encryption helps protect the privacy
105 of people you communicate with, and makes life difficult for bulk surveillance
106 systems. If you do have something important to hide, you're in good company;
107 these are the same tools that whistleblowers use to protect their identities
108 while shining light on human rights abuses, corruption and other crimes.
</p>
110 <p>In addition to using encryption, standing up
111 to surveillance requires fighting politically for a
<a
112 href=
"http://gnu.org/philosophy/surveillance-vs-democracy.html">reduction
113 in the amount of data collected on us
</a>, but the essential first step is
114 to protect yourself and make surveillance of your communication as difficult
115 as possible. This guide helps you do that. It is designed for beginners, but
116 if you already know the basics of GnuPG or are an experienced free software
117 user, you'll enjoy the advanced tips and the
<a href=
"workshops.html">guide
118 to teaching your friends
</a>.
</p>
120 </div><!-- End .intro -->
121 </div></header><!-- End #header -->
123 <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
124 <section class=
"row" id=
"section1"><div>
126 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
127 <div class=
"section-intro">
129 <h2><em>#
1</em> Get the pieces
</h2>
131 <p class=
"notes">This guide relies on software which is
<a
132 href=
"https://www.gnu.org/philosophy/free-sw.html">freely licensed
</a>; it's
133 completely transparent and anyone can copy it or make their own version. This
134 makes it safer from surveillance than proprietary software (like Windows or Mac
135 OS). To defend your freedom as well as protect yourself from surveillance, we
136 recommend you switch to a free software operating system like GNU/Linux. Learn
137 more about free software at
<a href=
"https://u.fsf.org/ys">fsf.org
</a>.
</p>
139 <p>To get started, you'll need the IceDove desktop email program installed
140 on your computer. For your system, IceDove may be known by the alternate name
141 "Thunderbird." Email programs are another way to access the same email accounts
142 you can access in a browser (like Gmail), but provide extra features.
</p>
144 <p>If you already have an email program, you can skip to
<a
145 href=
"#step-1b">Step
1.b
</a>.
</p>
147 </div><!-- End .section-intro -->
149 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
150 <div id=
"step-1a" class=
"step">
151 <div class=
"sidebar">
154 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png"
155 alt=
"Step 1.A: Install Wizard" /></p>
157 </div><!-- /.sidebar -->
160 <h3><em>Step
1.a
</em> Set up your email program with your email account
</h3>
162 <p>Open your email program and follow the wizard (step-by-step walkthrough)
163 that sets it up with your email account.
</p>
165 <p>Look for the letters SSL, TLS, or STARTTLS to the right of the servers
166 when you're setting up your account. If you don't see them, you will still
167 be able to use encryption, but this means that the people running your email
168 system are running behind the industry standard in protecting your security
169 and privacy. We recommend that you send them a friendly email asking them
170 to enable SSL, TLS, or STARTTLS for your email server. They will know what
171 you're talking about, so it's worth making the request even if you aren't
172 an expert on these security systems.
</p>
174 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
175 <div class=
"troubleshooting">
177 <h4>Troubleshooting
</h4>
180 <dt>The wizard doesn't launch
</dt>
181 <dd>You can launch the wizard yourself, but the menu option for doing so is
182 named differently in each email program. The button to launch it will be in
183 the program's main menu, under
"New" or something similar, titled something
184 like
"Add account" or
"New/Existing email account."</dd>
186 <dt>The wizard can't find my account or isn't downloading my mail
</dt>
187 <dd>Before searching the Web, we recommend you start by asking other people
188 who use your email system, to figure out the correct settings.
</dd>
190 <dt class=
"feedback">Don't see a solution to your problem?
</dt>
191 <dd class=
"feedback">Please let us know on the
<a
192 href=
"https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
196 </div><!-- /.troubleshooting -->
197 </div><!-- End .main -->
198 </div><!-- End #step1-a .step -->
200 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
201 <div id=
"step-1b" class=
"step">
204 <h3><em>Step
1.b
</em> Get GnuPG by downloading GPGTools
</h3>
206 <p>GPGTools is a software package that includes GnuPG.
<a
207 href=
"https://gpgtools.org/#gpgsuite">Download
</a> and install it, choosing
208 default options whenever asked. After it's installed, you can close any
209 windows that it creates.
</p>
211 <p>There are major security flaws in versions of GnuPG provided by GPGTools
212 prior to
2018.3. Make sure you have GPGTools
2018.3 or later.
</p>
214 </div><!-- End .main -->
215 </div><!-- End #step1-b .step -->
217 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
218 <div id=
"step-1c" class=
"step">
219 <div class=
"sidebar">
221 <li><img src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png"
222 alt=
"Step 1.C: Tools -> Add-ons" /></li>
223 <li><img src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png"
224 alt=
"Step 1.C: Search Add-ons" /></li>
225 <li><img src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png"
226 alt=
"Step 1.C: Install Add-ons" /></li>
229 </div><!-- /.sidebar -->
232 <h3><em>Step
1.c
</em> Install the Enigmail plugin for your email program
</h3>
234 <p>In your email program's menu, select Add-ons (it may be in the Tools
235 section). Make sure Extensions is selected on the left. Do you see Enigmail?
236 Make sure it's the latest version. If so, skip this step.
</p>
238 <p>If not, search
"Enigmail" with the search bar in the upper right. You
239 can take it from here. Restart your email program when you're done.
</p>
241 <p>There are major security flaws in Enigmail prior to version
2.0.7. Make
242 sure you have Enigmail
2.0.7 or later.
</p>
244 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
245 <div class=
"troubleshooting">
247 <h4>Troubleshooting
</h4>
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>
254 <dt>My email looks weird
</dt>
255 <dd>Enigmail doesn't tend to play nice with HTML, which is used to format
256 emails, so it may disable your HTML formatting automatically. To send an
257 HTML-formatted email without encryption or a signature, hold down the Shift
258 key when you select compose. You can then write an email as if Enigmail
261 <dt class=
"feedback">Don't see a solution to your problem?
</dt>
262 <dd class=
"feedback">Please let us know on the
<a
263 href=
"https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
267 </div><!-- /.troubleshooting -->
268 </div><!-- End .main -->
269 </div><!-- End #step-1b .step -->
270 </div></section><!-- End #section1 -->
272 <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
273 <section class=
"row" id=
"section2"><div>
275 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
276 <div class=
"section-intro">
278 <h2><em>#
2</em> Make your keys
</h2>
280 <p>To use the GnuPG system, you'll need a public key and a private key (known
281 together as a keypair). Each is a long string of randomly generated numbers
282 and letters that are unique to you. Your public and private keys are linked
283 together by a special mathematical function.
</p>
285 <p>Your public key isn't like a physical key, because it's stored in the open
286 in an online directory called a keyserver. People download it and use it,
287 along with GnuPG, to encrypt emails they send to you. You can think of the
288 keyserver as a phonebook; people who want to send you encrypted email can
289 look up your public key.
</p>
291 <p>Your private key is more like a physical key, because you keep it to
292 yourself (on your computer). You use GnuPG and your private key together to
293 descramble encrypted emails other people send to you.
<span style=
"font-weight:
294 bold;">You should never share your private key with anyone, under any
295 circumstances.
</span></p>
297 <p>In addition to encryption and decryption, you can also use these keys to
298 sign messages and check the authenticity of other people's signatures. We'll
299 discuss this more in the next section.
</p>
301 </div><!-- End .section-intro -->
303 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
304 <div id=
"step-2a" class=
"step">
305 <div class=
"sidebar">
308 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png"
309 alt=
"Step 2.A: Make a Keypair" /></p>
311 </div><!-- /.sidebar -->
314 <h3><em>Step
2.a
</em> Make a keypair
</h3>
316 <p>The Enigmail Setup wizard may start automatically. If it doesn't, select
317 Enigmail
→ Setup Wizard from your email program's menu. You don't need
318 to read the text in the window that pops up unless you'd like to, but it's
319 good to read the text on the later screens of the wizard. Click Next with
320 the default options selected, except in these instances, which are listed
321 in the order they appear:
</p>
324 <li>On the screen titled
"Encryption," select
"Encrypt all of my messages
325 by default, because privacy is critical to me."</li>
327 <li>On the screen titled
"Signing," select
"Don't sign my messages by
330 <li>On the screen titled
"Key Selection," select
"I want to create a new
331 key pair for signing and encrypting my email."</li>
333 <li>On the screen titled
"Create Key," pick a strong password! You can
334 do it manually, or you can use the Diceware method. Doing it manually
335 is faster but not as secure. Using Diceware takes longer and requires
336 dice, but creates a password that is much harder for attackers to figure
337 out. To use it, read the section
"Make a secure passphrase with Diceware" in
<a
338 href=
"https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">
339 this article
</a> by Micah Lee.
</li>
342 <p>If you'd like to pick a password manually, come up with something
343 you can remember which is at least twelve characters long, and includes
344 at least one lower case and upper case letter and at least one number or
345 punctuation symbol. Never pick a password you've used elsewhere. Don't use
346 any recognizable patterns, such as birthdays, telephone numbers, pets' names,
347 song lyrics, quotes from books, and so on.
</p>
349 <p class=
"notes">The program will take a little while to finish the next
350 step, the
"Key Creation" screen. While you wait, do something else with your
351 computer, like watching a movie or browsing the Web. The more you use the
352 computer at this point, the faster the key creation will go.
</p>
354 <p><span style=
"font-weight: bold;">When the
"Key Generation Completed" screen
355 pops up, select Generate Certificate and choose to save it in a safe place on
356 your computer (we recommend making a folder called
"Revocation Certificate"
357 in your home folder and keeping it there). This step is essential for your
358 email self-defense, as you'll learn more about in
<a href=
"#section5">Section
361 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
362 <div class=
"troubleshooting">
364 <h4>Troubleshooting
</h4>
367 <dt>I can't find the Enigmail menu.
</dt>
368 <dd>In many new email programs, the main menu is represented by an image
369 of three stacked horizontal bars. Enigmail may be inside a section called
372 <dt>More resources
</dt>
373 <dd>If you're having trouble with our
374 instructions or just want to learn more, check out
<a
375 href=
"https://www.enigmail.net/documentation/Key_Management#Generating_your_own_key_pair">
376 Enigmail's wiki instructions for key generation
</a>.
</dd>
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
384 </div><!-- /.troubleshooting -->
386 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
387 <div class=
"troubleshooting">
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>
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>
412 </div><!-- /.troubleshooting -->
413 </div><!-- End .main -->
414 </div><!-- End #step-2a .step -->
416 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
417 <div id=
"step-2b" class=
"step">
420 <h3><em>Step
2.b
</em> Upload your public key to a keyserver
</h3>
422 <p>In your email program's menu, select Enigmail
→ Key Management.
</p>
424 <p>Right click on your key and select Upload Public Keys to Keyserver. Use
425 the default keyserver in the popup.
</p>
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>
433 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
434 <div class=
"troubleshooting">
436 <h4>Troubleshooting
</h4>
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
444 <dt>My key doesn't appear in the list
</dt>
445 <dd>Try checking
"Display All Keys by Default."</dd>
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/Key_Management#Distributing_your_public_key">
451 Enigmail's documentation
</a>.
</dd>
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
459 </div><!-- /.troubleshooting -->
461 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
462 <div class=
"troubleshooting">
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>
476 </div><!-- /.troubleshooting -->
477 </div><!-- End .main -->
478 </div><!-- End #step-2b .step -->
480 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
481 <div id=
"terminology" class=
"step">
484 <h3>GnuPG, OpenPGP, what?
</h3>
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>
492 </div><!-- End .main -->
493 </div><!-- End #terminology.step-->
494 </div></section><!-- End #section2 -->
496 <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
497 <section class=
"row" id=
"section3"><div>
499 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
500 <div class=
"section-intro">
502 <h2><em>#
3</em> Try it out!
</h2>
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>
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 -->
514 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
515 <div id=
"step-3a" class=
"step">
516 <div class=
"sidebar">
519 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png"
520 alt=
"Try it out." /></p>
522 </div><!-- /.sidebar -->
525 <h3><em>Step
3.a
</em> Send Edward your public key
</h3>
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
→ 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>
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>
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>
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>
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>
552 </div><!-- End .main -->
553 </div><!-- End #step-3a .step -->
555 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
556 <div id=
"step-3b" class=
"step">
559 <h3><em>Step
3.b
</em> Send a test encrypted email
</h3>
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>
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>
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>
571 <p>Click Send. Enigmail will pop up a window that says
"Recipients not valid,
572 not trusted or not found."</p>
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>
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>
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>
587 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
588 <div class=
"troubleshooting">
590 <h4>Troubleshooting
</h4>
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>
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>
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://www.enigmail.net/documentation/Signature_and_Encryption#Encrypting_a_message">
608 Enigmail's wiki
</a>.
</dd>
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
616 </div><!-- /.troubleshooting -->
618 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
619 <div class=
"troubleshooting">
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>
631 </div><!-- /.troubleshooting -->
632 </div><!-- End .main -->
633 </div><!-- End #step-3b .step -->
635 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
636 <div id=
"step-headers_unencrypted" class=
"step">
639 <h3><em>Important:
</em> Security tips
</h3>
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>
649 <p>For greater security against potential attacks, you can turn off
650 HTML. Instead, you can render the message body as plain text.
</p>
652 </div><!-- End .main -->
653 </div><!-- End #step-headers_unencrypted .step-->
655 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
656 <div id=
"step-3c" class=
"step">
659 <h3><em>Step
3.c
</em> Receive a response
</h3>
661 <p>When Edward receives your email, he will use his private key to decrypt
662 it, then reply to you.
</p>
664 <p class=
"notes">It may take two or three minutes for Edward to
665 respond. In the meantime, you might want to skip ahead and check out the
<a
666 href=
"#section5">Use it Well
</a> section of this guide.
</p>
668 </div><!-- End .main -->
669 </div><!-- End #step-3c .step -->
671 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
672 <div id=
"step-3d" class=
"step">
675 <h3><em>Step
3.d
</em> Send a test signed email
</h3>
677 <p>GnuPG includes a way for you to sign messages and files, verifying that
678 they came from you and that they weren't tampered with along the way. These
679 signatures are stronger than their pen-and-paper cousins -- they're impossible
680 to forge, because they're impossible to create without your private key
681 (another reason to keep your private key safe).
</p>
683 <p>You can sign messages to anyone, so it's a great way to make people
684 aware that you use GnuPG and that they can communicate with you securely. If
685 they don't have GnuPG, they will be able to read your message and see your
686 signature. If they do have GnuPG, they'll also be able to verify that your
687 signature is authentic.
</p>
689 <p>To sign an email to Edward, compose any message to him and click the
690 pencil icon next to the lock icon so that it turns gold. If you sign a
691 message, GnuPG may ask you for your password before it sends the message,
692 because it needs to unlock your private key for signing.
</p>
694 <p>With the lock and pencil icons, you can choose whether each message will
695 be encrypted, signed, both, or neither.
</p>
700 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
701 <div id=
"step-3e" class=
"step">
704 <h3><em>Step
3.e
</em> Receive a response
</h3>
706 <p>When Edward receives your email, he will use your public key (which
707 you sent him in
<a href=
"#step-3a">Step
3.A
</a>) to verify the message
708 you sent has not been tampered with and to encrypt his reply to you.
</p>
710 <p class=
"notes">It may take two or three minutes for Edward to
711 respond. In the meantime, you might want to skip ahead and check out the
<a
712 href=
"#section5">Use it Well
</a> section of this guide.
</p>
714 <p>Edward's reply will arrive encrypted, because he prefers to use encryption
715 whenever possible. If everything goes according to plan, it should say
716 "Your signature was verified." If your test signed email was also encrypted,
717 he will mention that first.
</p>
719 <p>When you receive Edward's email and open it, Enigmail will
720 automatically detect that it is encrypted with your public key, and
721 then it will use your private key to decrypt it.
</p>
723 <p>Notice the bar that Enigmail shows you above the message, with
724 information about the status of Edward's key.
</p>
726 </div><!-- End .main -->
727 </div><!-- End #step-3e .step -->
730 <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
731 <section class=
"row" id=
"section4"><div>
733 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
734 <div class=
"section-intro">
736 <h2><em>#
4</em> Learn the Web of Trust
</h2>
738 <p>Email encryption is a powerful technology, but it has a weakness;
739 it requires a way to verify that a person's public key is actually
740 theirs. Otherwise, there would be no way to stop an attacker from making
741 an email address with your friend's name, creating keys to go with it and
742 impersonating your friend. That's why the free software programmers that
743 developed email encryption created keysigning and the Web of Trust.
</p>
745 <p>When you sign someone's key, you are publicly saying that you've verified
746 that it belongs to them and not someone else.
</p>
748 <p>Signing keys and signing messages use the same type of mathematical
749 operation, but they carry very different implications. It's a good practice
750 to generally sign your email, but if you casually sign people's keys, you
751 may accidently end up vouching for the identity of an imposter.
</p>
753 <p>People who use your public key can see who has signed it. Once you've
754 used GnuPG for a long time, your key may have hundreds of signatures. You
755 can consider a key to be more trustworthy if it has many signatures from
756 people that you trust. The Web of Trust is a constellation of GnuPG users,
757 connected to each other by chains of trust expressed through signatures.
</p>
759 </div><!-- End .section-intro -->
761 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
762 <div id=
"step-4a" class=
"step">
763 <div class=
"sidebar">
766 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png"
767 alt=
"Section 4: Web of Trust" /></p>
769 </div><!-- /.sidebar -->
772 <h3><em>Step
4.a
</em> Sign a key
</h3>
774 <p>In your email program's menu, go to Enigmail
→ Key Management.
</p>
776 <p>Right click on Edward's public key and select Sign Key from the context
779 <p>In the window that pops up, select
"I will not answer" and click ok.
</p>
781 <p>Now you should be back at the Key Management menu. Select Keyserver
→
782 Upload Public Keys and hit ok.
</p>
784 <p class=
"notes">You've just effectively said
"I trust that Edward's public
785 key actually belongs to Edward." This doesn't mean much because Edward isn't
786 a real person, but it's good practice.
</p>
788 <!--<div id="pgp-pathfinder">
790 <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi"
793 <p><strong>From:</strong><input type="text" value="xD41A008"
796 <p><strong>To:</strong><input type="text" value="50BD01x4" name="TO"></p>
798 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"><input
799 type="reset" value="reset" name=".reset"></p>
803 </div>End #pgp-pathfinder -->
804 </div><!-- End .main -->
805 </div><!-- End #step-4a .step -->
807 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
808 <div id=
"step-identify_keys" class=
"step">
811 <h3>Identifying keys: Fingerprints and IDs
</h3>
813 <p>People's public keys are usually identified by their key fingerprint,
814 which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8
815 (for Edward's key). You can see the fingerprint for your public key, and
816 other public keys saved on your computer, by going to Enigmail
→ Key
817 Management in your email program's menu, then right clicking on the key
818 and choosing Key Properties. It's good practice to share your fingerprint
819 wherever you share your email address, so that people can double-check that
820 they have the correct public key when they download yours from a keyserver.
</p>
822 <p class=
"notes">You may also see public keys referred to by a shorter
823 key ID. This key ID is visible directly from the Key Management
824 window. These eight character key IDs were previously used for
825 identification, which used to be safe, but is no longer reliable. You
826 need to check the full fingerprint as part of verifying you have the
827 correct key for the person you are trying to contact. Spoofing, in
828 which someone intentionally generates a key with a fingerprint whose
829 final eight characters are the same as another, is unfortunately
832 </div><!-- End .main -->
833 </div><!-- End #step-identify_keys .step-->
835 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
836 <div id=
"check-ids-before-signing" class=
"step">
839 <h3><em>Important:
</em> What to consider when signing keys
</h3>
841 <p>Before signing a person's key, you need to be confident that it actually
842 belongs to them, and that they are who they say they are. Ideally, this
843 confidence comes from having interactions and conversations with them over
844 time, and witnessing interactions between them and others. Whenever signing
845 a key, ask to see the full public key fingerprint, and not just the shorter
846 key ID. If you feel it's important to sign the key of someone you've just
847 met, also ask them to show you their government identification, and make
848 sure the name on the ID matches the name on the public key. In Enigmail,
849 answer honestly in the window that pops up and asks
"How carefully have you
850 verified that the key you are about to sign actually belongs to the person(s)
853 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
854 <div class=
"troubleshooting">
859 <dt>Master the Web of Trust
</dt>
860 <dd>Unfortunately, trust does not spread between users the way
<a
861 href=
"http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people
862 think
</a>. One of best ways to strengthen the GnuPG community is to deeply
<a
863 href=
"https://www.gnupg.org/gph/en/manual/x334.html">understand
</a> the Web of
864 Trust and to carefully sign as many people's keys as circumstances permit.
</dd>
866 <dt>Set ownertrust
</dt>
867 <dd>If you trust someone enough to validate other people's keys, you can assign
868 them an ownertrust level through Enigmails's key management window. Right
869 click on the other person's key, go to the
"Select Owner Trust" menu option,
870 select the trustlevel and click OK. Only do this once you feel you have a
871 deep understanding of the Web of Trust.
</dd>
874 </div><!-- /.troubleshooting -->
875 </div><!-- End .main -->
876 </div><!-- End #check-ids-before-signing .step-->
877 </div></section><!-- End #section4 -->
879 <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
880 <section id=
"section5" class=
"row"><div>
882 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
883 <div class=
"section-intro">
885 <h2><em>#
5</em> Use it well
</h2>
887 <p>Everyone uses GnuPG a little differently, but it's important to follow
888 some basic practices to keep your email secure. Not following them, you
889 risk the privacy of the people you communicate with, as well as your own,
890 and damage the Web of Trust.
</p>
892 </div><!-- End .section-intro -->
894 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
895 <div id=
"step-5a" class=
"step">
896 <div class=
"sidebar">
899 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png"
900 alt=
"Section 5: Use it Well (1)" /></p>
902 </div><!-- /.sidebar -->
905 <h3>When should I encrypt? When should I sign?
</h3>
907 <p>The more you can encrypt your messages, the better. If you only encrypt
908 emails occasionally, each encrypted message could raise a red flag for
909 surveillance systems. If all or most of your email is encrypted, people
910 doing surveillance won't know where to start. That's not to say that only
911 encrypting some of your email isn't helpful -- it's a great start and it
912 makes bulk surveillance more difficult.
</p>
914 <p>Unless you don't want to reveal your own identity (which requires other
915 protective measures), there's no reason not to sign every message, whether or
916 not you are encrypting. In addition to allowing those with GnuPG to verify
917 that the message came from you, signing is a non-intrusive way to remind
918 everyone that you use GnuPG and show support for secure communication. If you
919 often send signed messages to people that aren't familiar with GnuPG, it's
920 nice to also include a link to this guide in your standard email signature
921 (the text kind, not the cryptographic kind).
</p>
923 </div><!-- End .main -->
924 </div><!-- End #step-5a .step -->
926 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
927 <div id=
"step-5b" class=
"step">
928 <div class=
"sidebar">
931 src=
"//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png"
932 alt=
"Section 5: Use it Well (2)" /></p>
934 </div><!-- /.sidebar -->
937 <h3>Be wary of invalid keys
</h3>
939 <p>GnuPG makes email safer, but it's still important to watch out for invalid
940 keys, which might have fallen into the wrong hands. Email encrypted with
941 invalid keys might be readable by surveillance programs.
</p>
943 <p>In your email program, go back to the first encrypted email that Edward
944 sent you. Because Edward encrypted it with your public key, it will have a
945 message from Enigmail at the top, which most likely says
"Enigmail: Part of
946 this message encrypted."</p>
948 <p><b>When using GnuPG, make a habit of glancing at that bar. The program
949 will warn you there if you get an email signed with a key that can't
952 </div><!-- End .main -->
953 </div><!-- End #step-5b .step -->
955 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
956 <div id=
"step-5c" class=
"step">
959 <h3>Copy your revocation certificate to somewhere safe
</h3>
961 <p>Remember when you created your keys and saved the revocation certificate
962 that GnuPG made? It's time to copy that certificate onto the safest digital
963 storage that you have -- the ideal thing is a flash drive, disk, or hard
964 drive stored in a safe place in your home, not on a device you carry with
967 <p>If your private key ever gets lost or stolen, you'll need this certificate
968 file to let people know that you are no longer using that keypair.
</p>
970 </div><!-- End .main -->
971 </div><!-- End #step-5c .step -->
973 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
974 <div id=
"step-lost_key" class=
"step">
977 <h3><em>Important:
</em> act swiftly if someone gets your private key
</h3>
979 <p>If you lose your private key or someone else gets ahold
980 of it (say, by stealing or cracking your computer), it's
981 important to revoke it immediately before someone else uses
982 it to read your encrypted email or forge your signature. This
983 guide doesn't cover how to revoke a key, but you can follow these
<a
984 href=
"https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions
</a>.
985 After you're done revoking, make a new key and send an email to everyone
986 with whom you usually use your key to make sure they know, including a copy
989 </div><!-- End .main -->
990 </div><!-- End #step-lost_key .step-->
992 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
993 <!---<div id="transfer-key" class="step">
996 <h3>Transferring you key</h3>
998 <p>You can use Enigmail's <a
999 href="https://www.enigmail.net/documentation/Key_Management">key management
1000 window</a> to import and export keys. If you want to be able to read
1001 your encrypted email on a different computer, you will need to export
1002 your secret key from here. Be warned, if you transfer the key without <a
1003 href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a>
1004 the drive it's on the transfer will be dramatically less secure.</p>
1006 </div>--><!-- End .main
1007 </div> End #transfer-key .step-->
1009 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1010 <div id=
"webmail-and-GnuPG" class=
"step">
1013 <h3>Webmail and GnuPG
</h3>
1015 <p>When you use a web browser to access your email, you're using webmail,
1016 an email program stored on a distant website. Unlike webmail, your desktop
1017 email program runs on your own computer. Although webmail can't decrypt
1018 encrypted email, it will still display it in its encrypted form. If you
1019 primarily use webmail, you'll know to open your email client when you receive
1020 a scrambled email.
</p>
1022 </div><!-- End .main -->
1023 </div><!-- End #webmail-and-GnuPG .step-->
1025 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
1026 <div id="step-5d" class="step">
1029 <h3>Make your public key part of your online identity</h3>
1031 <p> First add your public key fingerprint to your email signature, then
1032 compose an email to at least five of your friends, telling them you just
1033 set up GnuPG and mentioning your public key fingerprint. Link to this guide
1034 and ask them to join you. Don't forget that there's also an awesome <a
1035 href="infographic.html">infographic to share.</a></p>
1037 <p class="notes">Start writing your public key fingerprint anywhere someone
1038 would see your email address: your social media profiles, blog, Website,
1039 or business card. (At the Free Software Foundation, we put ours on our
1040 <a href="https://fsf.org/about/staff">staff page</a>.) We need to get our
1041 culture to the point that we feel like something is missing when we see an
1042 email address without a public key fingerprint.</p>
1044 </div>--><!-- End .main
1045 </div> End #step-5d .step-->
1046 </div></section><!-- End #section5 -->
1048 <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
1049 <section class=
"row" id=
"section6">
1050 <div id=
"step-click_here" class=
"step">
1053 <h2><a href=
"next_steps.html">Great job! Check out the next steps.
</a></h2>
1055 </div><!-- End .main -->
1056 </div><!-- End #step-click_here .step-->
1057 </section><!-- End #section6 -->
1059 <!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
1060 <!-- When un-commenting this section go to main.css and search
1061 for /* Guide Sections Background */ then add #faq to the desired color
1062 <section class="row" id="faq"><div>
1063 <div class="sidebar">
1071 <dt>My key expired</dt>
1072 <dd>Answer coming soon.</dd>
1074 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
1075 <dd>Answer coming soon.</dd>
1077 <dt>My email program is opening at times I don't want it to open/is now my
1078 default program and I don't want it to be.</dt>
1079 <dd>Answer coming soon.</dd>
1084 </section> --><!-- End #faq -->
1086 <!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
1087 <footer class=
"row" id=
"footer"><div>
1088 <div id=
"copyright">
1090 <h4><a href=
"https://u.fsf.org/ys"><img
1091 alt=
"Free Software Foundation"
1092 src=
"//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" /></a></h4>
1094 <p>Copyright
© 2014-
2016 <a
1095 href=
"https://u.fsf.org/ys">Free Software Foundation
</a>, Inc.
<a
1096 href=
"https://my.fsf.org/donate/privacypolicy.html">Privacy Policy
</a>. Please
1097 support our work by
<a href=
"https://u.fsf.org/yr">joining us as an associate
1100 <p>The images on this page are under a
<a
1101 href=
"https://creativecommons.org/licenses/by/4.0/">Creative Commons
1102 Attribution
4.0 license (or later version)
</a>, and the rest of it is under
1103 a
<a href=
"https://creativecommons.org/licenses/by-sa/4.0">Creative Commons
1104 Attribution-ShareAlike
4.0 license (or later version)
</a>. Download the
<a
1105 href=
"http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
1106 source code of Edward reply bot
</a> by Andrew Engelbrecht
1107 <sudoman@ninthfloor.org
> and Josh Drake
<zamnedix@gnu.org
>,
1108 available under the GNU Affero General Public License.
<a
1109 href=
"http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these
1112 <p>Fonts used in the guide
& infographic:
<a
1113 href=
"https://www.google.com/fonts/specimen/Dosis">Dosis
</a> by Pablo
1114 Impallari,
<a href=
"http://www.google.com/fonts/specimen/Signika">Signika
</a>
1115 by Anna Giedry
ś,
<a
1116 href=
"http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo
1117 Narrow
</a> by Omnibus-Type,
<a
1118 href=
"https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-
2000</a>
1119 by Florian Cramer.
</p>
1121 <p>Download the
<a href=
"emailselfdefense_source.zip">source package
</a>
1122 for this guide, including fonts, image source files and the text of Edward's
1125 <p>This site uses the Weblabels standard for labeling
<a
1126 href=
"https://www.fsf.org/campaigns/freejs">free JavaScript
</a>. View
1127 the JavaScript
<a href=
"//weblabels.fsf.org/emailselfdefense.fsf.org/"
1128 rel=
"jslicense">source code and license information
</a>.
</p>
1130 </div><!-- /#copyright -->
1132 <p class=
"credits">Infographic and guide design by
<a rel=
"external"
1133 href=
"http://jplusplus.org"><strong>Journalism++
</strong><img
1134 src=
"//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png"
1135 alt=
"Journalism++" /></a></p><!-- /.credits -->
1136 </div></footer><!-- End #footer -->
1139 <script type=
"text/javascript"
1140 src=
"//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
1141 <script type=
"text/javascript"
1142 src=
"//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
1144 <script type=
"text/javascript" ><!--
1145 // @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
1146 var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");
1147 document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
1149 var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);
1150 piwikTracker.trackPageView();
1151 piwikTracker.enableLinkTracking();
1156 src=
"//piwik.fsf.org/piwik.php?idsite=13" style=
"border:0"
1157 alt=
"" /></p></noscript>
1158 <!-- End Piwik Tracking Code -->