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