en/index.html

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