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