en/mac.html

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