en/index.html

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