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