en/index.html

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