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