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 - v4.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">简体中文 - v4.0</a></li>
  46 <li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
  47 <strong><span 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 class="spacer"><a href="workshops.html">Teach your friends</a></li>
  55 <li class="spacer"><a
  56 href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email encryption for everyone via %40fsf">
  57 Share&nbsp;
  58 <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class="share-logo"
  59 alt="[GNU Social]" />&nbsp;
  60 <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png" class="share-logo"
  61 alt="[Pump.io]" />&nbsp;
  62 <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" class="share-logo"
  63 alt="[Reddit]" />&nbsp;
  64 <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" class="share-logo"
  65 alt="[Hacker News]" /></a></li>
  66 </ul>
  67
  68 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
  69 <div id="fsf-intro">
  70
  71 <h3><a href="http://u.fsf.org/ys"><img
  72 alt="Free Software Foundation"
  73 src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
  74 </a></h3>
  75
  76 <div class="fsf-emphasis">
  77
  78 <p>We fight for computer users' rights, and promote the development of free (as
  79 in freedom) software. Resisting bulk surveillance is very important to us.</p>
  80
  81 <p><strong>Please donate to support Email Self-Defense. We need to keep
  82 improving it, and making more materials, for the benefit of people around
  83 the world taking the first step towards protecting their privacy.</strong></p>
  84
  85 </div>
  86
  87 <p><a
  88 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
  89 alt="Donate"
  90 src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a></p>
  91
  92 </div><!-- End #fsf-intro -->
  93
  94 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
  95 <div class="intro">
  96
  97 <p><a id="infographic" href="infographic.html"><img
  98 src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png"
  99 alt="View &amp; share our infographic &rarr;" /></a>
 100 Bulk surveillance violates our fundamental rights and makes free speech
 101 risky. This guide will teach you a basic surveillance self-defense skill: email
 102 encryption. Once you've finished, you'll be able to send and receive emails
 103 that are scrambled to make sure a surveillance agent or thief intercepting
 104 your email can't read them. All you need is a computer with an Internet
 105 connection, an email account, and about forty minutes.</p>
 106
 107 <p>Even if you have nothing to hide, using encryption helps protect the privacy
 108 of people you communicate with, and makes life difficult for bulk surveillance
 109 systems. If you do have something important to hide, you're in good company;
 110 these are the same tools that whistleblowers use to protect their identities
 111 while shining light on human rights abuses, corruption and other crimes.</p>
 112
 113 <p>In addition to using encryption, standing up
 114 to surveillance requires fighting politically for a <a
 115 href="http://gnu.org/philosophy/surveillance-vs-democracy.html">reduction
 116 in the amount of data collected on us</a>, but the essential first step is
 117 to protect yourself and make surveillance of your communication as difficult
 118 as possible. This guide helps you do that. It is designed for beginners, but
 119 if you already know the basics of GnuPG or are an experienced free software
 120 user, you'll enjoy the advanced tips and the <a href="workshops.html">guide
 121 to teaching your friends</a>.</p>
 122
 123 </div><!-- End .intro -->
 124 </div></header><!-- End #header -->
 125
 126 <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
 127 <section class="row" id="section1"><div>
 128
 129 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 130 <div class="section-intro">
 131
 132 <h2><em>#1</em> Get the pieces</h2>
 133
 134 <p class="notes">This guide relies on software which is <a
 135 href="https://www.gnu.org/philosophy/free-sw.html">freely licensed</a>; it's
 136 completely transparent and anyone can copy it or make their own version. This
 137 makes it safer from surveillance than proprietary software (like Windows or Mac
 138 OS). To defend your freedom as well as protect yourself from surveillance, we
 139 recommend you switch to a free software operating system like GNU/Linux. Learn
 140 more about free software at <a href="https://u.fsf.org/ys">fsf.org</a>.</p>
 141
 142 <p>To get started, you'll need the IceDove desktop email program installed
 143 on your computer. For your system, IceDove may be known by the alternate name
 144 "Thunderbird." Email programs are another way to access the same email accounts
 145 you can access in a browser (like Gmail), but provide extra features.</p>
 146
 147 <p>If you already have an email program, you can skip to <a
 148 href="#step-1b">Step 1.b</a>.</p>
 149
 150 </div><!-- End .section-intro -->
 151
 152 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 153 <div id="step-1a" class="step">
 154 <div class="sidebar">
 155
 156 <p><img
 157 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png"
 158 alt="Step 1.A: Install Wizard" /></p>
 159
 160 </div><!-- /.sidebar -->
 161 <div class="main">
 162
 163 <h3><em>Step 1.a</em> Set up your email program with your email account</h3>
 164
 165 <p>Open your email program and follow the wizard (step-by-step walkthrough)
 166 that sets it up with your email account.</p>
 167
 168 <p>Look for the letters SSL, TLS, or STARTTLS to the right of the servers
 169 when you're setting up your account. If you don't see them, you will still
 170 be able to use encryption, but this means that the people running your email
 171 system are running behind the industry standard in protecting your security
 172 and privacy. We recommend that you send them a friendly email asking them
 173 to enable SSL, TLS, or STARTTLS for your email server. They will know what
 174 you're talking about, so it's worth making the request even if you aren't
 175 an expert on these security systems.</p>
 176
 177 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 178 <div class="troubleshooting">
 179
 180 <h4>Troubleshooting</h4>
 181
 182 <dl>
 183 <dt>The wizard doesn't launch</dt>
 184 <dd>You can launch the wizard yourself, but the menu option for doing so is
 185 named differently in each email program. The button to launch it will be in
 186 the program's main menu, under "New" or something similar, titled something
 187 like "Add account" or "New/Existing email account."</dd>
 188
 189 <dt>The wizard can't find my account or isn't downloading my mail</dt>
 190 <dd>Before searching the Web, we recommend you start by asking other people
 191 who use your email system, to figure out the correct settings.</dd>
 192
 193 <dt class="feedback">Don't see a solution to your problem?</dt>
 194 <dd class="feedback">Please let us know on the <a
 195 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 196 page</a>.</dd>
 197 </dl>
 198
 199 </div><!-- /.troubleshooting -->
 200 </div><!-- End .main -->
 201 </div><!-- End #step1-a .step -->
 202
 203 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 204 <div id="step-1b" class="step">
 205 <div class="main">
 206
 207 <h3><em>Step 1.b</em> Get GnuPG by downloading GPGTools</h3>
 208
 209 <p>GPGTools is a software package that includes GnuPG. <a
 210 href="https://gpgtools.org/#gpgsuite">Download</a> and install it, choosing
 211 default options whenever asked. After it's installed, you can close any
 212 windows that it creates.</p>
 213
 214 <p>There are major security flaws in versions of GnuPG provided by GPGTools
 215 prior to 2018.3. Make sure you have GPGTools 2018.3 or later.</p>
 216
 217 </div><!-- End .main -->
 218 </div><!-- End #step1-b .step -->
 219
 220 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 221 <div id="step-1c" class="step">
 222 <div class="sidebar">
 223 <ul class="images">
 224 <li><img 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 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png"
 227 alt="Step 1.C: Search Add-ons" /></li>
 228 <li><img 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?
 239 Make sure it's the latest version. If 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>There are major security flaws in Enigmail prior to version 2.0.7. Make
 245 sure you have Enigmail 2.0.7 or later.</p>
 246
 247 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 248 <div class="troubleshooting">
 249
 250 <h4>Troubleshooting</h4>
 251
 252 <dl>
 253 <dt>I can't find the menu.</dt>
 254 <dd>In many new email programs, the main menu is represented by an image of
 255 three stacked horizontal bars.</dd>
 256
 257 <dt>My email looks weird</dt>
 258 <dd>Enigmail doesn't tend to play nice with HTML, which is used to format
 259 emails, so it may disable your HTML formatting automatically. To send an
 260 HTML-formatted email without encryption or a signature, hold down the Shift
 261 key when you select compose. You can then write an email as if Enigmail
 262 wasn't there.</dd>
 263
 264 <dt class="feedback">Don't see a solution to your problem?</dt>
 265 <dd class="feedback">Please let us know on the <a
 266 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 267 page</a>.</dd>
 268 </dl>
 269
 270 </div><!-- /.troubleshooting -->
 271 </div><!-- End .main -->
 272 </div><!-- End #step-1b .step -->
 273 </div></section><!-- End #section1 -->
 274
 275 <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
 276 <section class="row" id="section2"><div>
 277
 278 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 279 <div class="section-intro">
 280
 281 <h2><em>#2</em> Make your keys</h2>
 282
 283 <p>To use the GnuPG system, you'll need a public key and a private key (known
 284 together as a keypair). Each is a long string of randomly generated numbers
 285 and letters that are unique to you. Your public and private keys are linked
 286 together by a special mathematical function.</p>
 287
 288 <p>Your public key isn't like a physical key, because it's stored in the open
 289 in an online directory called a keyserver. People download it and use it,
 290 along with GnuPG, to encrypt emails they send to you. You can think of the
 291 keyserver as a phonebook; people who want to send you encrypted email can
 292 look up your public key.</p>
 293
 294 <p>Your private key is more like a physical key, because you keep it to
 295 yourself (on your computer). You use GnuPG and your private key together to
 296 descramble encrypted emails other people send to you. <span style="font-weight:
 297 bold;">You should never share your private key with anyone, under any
 298 circumstances.</span></p>
 299
 300 <p>In addition to encryption and decryption, you can also use these keys to
 301 sign messages and check the authenticity of other people's signatures. We'll
 302 discuss this more in the next section.</p>
 303
 304 </div><!-- End .section-intro -->
 305
 306 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 307 <div id="step-2a" class="step">
 308 <div class="sidebar">
 309
 310 <p><img
 311 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png"
 312 alt="Step 2.A: Make a Keypair" /></p>
 313
 314 </div><!-- /.sidebar -->
 315 <div class="main">
 316
 317 <h3><em>Step 2.a</em> Make a keypair</h3>
 318
 319 <p>The Enigmail Setup wizard may start automatically. If it doesn't, select
 320 Enigmail &rarr; Setup Wizard from your email program's menu. You don't need
 321 to read the text in the window that pops up unless you'd like to, but it's
 322 good to read the text on the later screens of the wizard. Click Next with
 323 the default options selected, except in these instances, which are listed
 324 in the order they appear:</p>
 325
 326 <ul>
 327 <li>On the screen titled "Encryption," select "Encrypt all of my messages
 328 by default, because privacy is critical to me."</li>
 329
 330 <li>On the screen titled "Signing," select "Don't sign my messages by
 331 default."</li>
 332
 333 <li>On the screen titled "Key Selection," select "I want to create a new
 334 key pair for signing and encrypting my email."</li>
 335
 336 <li>On the screen titled "Create Key," pick a strong password! You can
 337 do it manually, or you can use the Diceware method. Doing it manually
 338 is faster but not as secure. Using Diceware takes longer and requires
 339 dice, but creates a password that is much harder for attackers to figure
 340 out. To use it, read the section "Make a secure passphrase with Diceware" in <a
 341 href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">
 342 this article</a> by Micah Lee.</li>
 343 </ul>
 344
 345 <p>If you'd like to pick a password manually, come up with something
 346 you can remember which is at least twelve characters long, and includes
 347 at least one lower case and upper case letter and at least one number or
 348 punctuation symbol. Never pick a password you've used elsewhere. Don't use
 349 any recognizable patterns, such as birthdays, telephone numbers, pets' names,
 350 song lyrics, quotes from books, and so on.</p>
 351
 352 <p class="notes">The program will take a little while to finish the next
 353 step, the "Key Creation" screen. While you wait, do something else with your
 354 computer, like watching a movie or browsing the Web. The more you use the
 355 computer at this point, the faster the key creation will go.</p>
 356
 357 <p><span style="font-weight: bold;">When the "Key Generation Completed" screen
 358 pops up, select Generate Certificate and choose to save it in a safe place on
 359 your computer (we recommend making a folder called "Revocation Certificate"
 360 in your home folder and keeping it there). This step is essential for your
 361 email self-defense, as you'll learn more about in <a href="#section5">Section
 362 5</a>.</span></p>
 363
 364 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 365 <div class="troubleshooting">
 366
 367 <h4>Troubleshooting</h4>
 368
 369 <dl>
 370 <dt>I can't find the Enigmail menu.</dt>
 371 <dd>In many new email programs, the main menu is represented by an image
 372 of three stacked horizontal bars. Enigmail may be inside a section called
 373 Tools.</dd>
 374
 375 <dt>More resources</dt>
 376 <dd>If you're having trouble with our
 377 instructions or just want to learn more, check out <a
 378 href="https://www.enigmail.net/documentation/Key_Management#Generating_your_own_key_pair">
 379 Enigmail's wiki instructions for key generation</a>.</dd>
 380
 381 <dt class="feedback">Don't see a solution to your problem?</dt>
 382 <dd class="feedback">Please let us know on the <a
 383 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 384 page</a>.</dd>
 385 </dl>
 386
 387 </div><!-- /.troubleshooting -->
 388
 389 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 390 <div class="troubleshooting">
 391
 392 <h4>Advanced</h4>
 393
 394 <dl>
 395 <dt>Command line key generation</dt>
 396 <dd>If you prefer using the command line for a higher
 397 degree of control, you can follow the documentation from <a
 398 href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy
 399 Handbook</a>. Make sure you stick with "RSA and RSA" (the default),
 400 because it's newer and more secure than the algorithms the documentation
 401 recommends. Also make sure your key is at least 2048 bits, or 4096 if you
 402 want to be extra secure.</dd>
 403
 404 <dt>Advanced key pairs</dt>
 405 <dd>When GnuPG creates a new keypair, it compartmentalizes
 406 the encryption function from the signing function through <a
 407 href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use
 408 subkeys carefully, you can keep your GnuPG identity much more
 409 secure and recover from a compromised key much more quickly. <a
 410 href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a>
 411 and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a>
 412 provide good guides for setting up a secure subkey configuration.</dd>
 413 </dl>
 414
 415 </div><!-- /.troubleshooting -->
 416 </div><!-- End .main -->
 417 </div><!-- End #step-2a .step -->
 418
 419 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 420 <div id="step-2b" class="step">
 421 <div class="main">
 422
 423 <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
 424
 425 <p>In your email program's menu, select Enigmail &rarr; Key Management.</p>
 426
 427 <p>Right click on your key and select Upload Public Keys to Keyserver. Use
 428 the default keyserver in the popup.</p>
 429
 430 <p class="notes">Now someone who wants to send you an encrypted message can
 431 download your public key from the Internet. There are multiple keyservers
 432 that you can select from the menu when you upload, but they are all copies
 433 of each other, so it doesn't matter which one you use. However, it sometimes
 434 takes a few hours for them to match each other when a new key is uploaded.</p>
 435
 436 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 437 <div class="troubleshooting">
 438
 439 <h4>Troubleshooting</h4>
 440
 441 <dl>
 442 <dt>The progress bar never finishes</dt>
 443 <dd>Close the upload popup, make sure you are connected to the Internet,
 444 and try again. If that doesn't work, try again, selecting a different
 445 keyserver.</dd>
 446
 447 <dt>My key doesn't appear in the list</dt>
 448 <dd>Try checking "Display All Keys by Default."</dd>
 449
 450 <dt>More documentation</dt>
 451 <dd>If you're having trouble with our
 452 instructions or just want to learn more, check out <a
 453 href="https://www.enigmail.net/documentation/Key_Management#Distributing_your_public_key">
 454 Enigmail's documentation</a>.</dd>
 455
 456 <dt class="feedback">Don't see a solution to your problem?</dt>
 457 <dd class="feedback">Please let us know on the <a
 458 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 459 page</a>.</dd>
 460 </dl>
 461
 462 </div><!-- /.troubleshooting -->
 463
 464 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 465 <div class="troubleshooting">
 466
 467 <h4>Advanced</h4>
 468
 469 <dl>
 470 <dt>Uploading a key from the command line</dt>
 471 <dd>You can also upload your keys to a keyserver through the <a
 472 href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a
 473 href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a>
 474 maintains a list of highly interconnected keyservers. You can also <a
 475 href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export
 476 your key</a> as a file on your computer.</dd>
 477 </dl>
 478
 479 </div><!-- /.troubleshooting -->
 480 </div><!-- End .main -->
 481 </div><!-- End #step-2b .step -->
 482
 483 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 484 <div id="terminology" class="step">
 485 <div class="main">
 486
 487 <h3>GnuPG, OpenPGP, what?</h3>
 488
 489 <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP
 490 are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the
 491 encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG)
 492 is the program that implements the standard. Enigmail is a plug-in program
 493 for your email program that provides an interface for GnuPG.</p>
 494
 495 </div><!-- End .main -->
 496 </div><!-- End #terminology.step-->
 497 </div></section><!-- End #section2 -->
 498
 499 <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
 500 <section class="row" id="section3"><div>
 501
 502 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 503 <div class="section-intro">
 504
 505 <h2><em>#3</em> Try it out!</h2>
 506
 507 <p>Now you'll try a test correspondence with a computer program named Edward,
 508 who knows how to use encryption. Except where noted, these are the same
 509 steps you'd follow when corresponding with a real, live person.</p>
 510
 511 <!-- <p>NOTE: Edward is currently having some technical difficulties, so he
 512 may take a long time to respond, or not respond at all. We're sorry about
 513 this and we're working hard to fix it. Your key will still work even without
 514 testing with Edward.</p> -->
 515 </div><!-- End .section-intro -->
 516
 517 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 518 <div id="step-3a" class="step">
 519 <div class="sidebar">
 520
 521 <p><img
 522 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png"
 523 alt="Try it out." /></p>
 524
 525 </div><!-- /.sidebar -->
 526 <div class="main">
 527
 528 <h3><em>Step 3.a</em> Send Edward your public key</h3>
 529
 530 <p>This is a special step that you won't have to do when corresponding
 531 with real people. In your email program's menu, go to Enigmail &rarr; Key
 532 Management. You should see your key in the list that pops up. Right click
 533 on your key and select Send Public Keys by Email. This will create a new
 534 draft message, as if you had just hit the Write button.</p>
 535
 536 <p>Address the message to <a
 537 href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word
 538 (whatever you want) in the subject and body of the email. Don't send yet.</p>
 539
 540 <p>The lock icon in the top left should be yellow, meaning encryption is
 541 turned on. We want this first special message to be unencrypted, so
 542 click the icon once to turn it off. The lock should become grey, with a
 543 blue dot on it (to alert you that the setting has been changed from the
 544 default). Once encryption is off, hit Send.</p>
 545
 546 <p class="notes">It may take two or three minutes for Edward to
 547 respond. In the meantime, you might want to skip ahead and check out the <a
 548 href="#section5">Use it Well</a> section of this guide. Once he's responded,
 549 head to the next step. From here on, you'll be doing just the same thing as
 550 when corresponding with a real person.</p>
 551
 552 <p>When you open Edward's reply, GnuPG may prompt you for your password
 553 before using your private key to decrypt it.</p>
 554
 555 </div><!-- End .main -->
 556 </div><!-- End #step-3a .step -->
 557
 558 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 559 <div id="step-3b" class="step">
 560 <div class="main">
 561
 562 <h3><em>Step 3.b</em> Send a test encrypted email</h3>
 563
 564 <p>Write a new email in your email program, addressed to <a
 565 href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject
 566 "Encryption test" or something similar and write something in the body.</p>
 567
 568 <p>The lock icon in the top left of the window should be yellow, meaning
 569 encryption is on. This will be your default from now on.</p>
 570
 571 <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll
 572 get to this in a moment.</p>
 573
 574 <p>Click Send. Enigmail will pop up a window that says "Recipients not valid,
 575 not trusted or not found."</p>
 576
 577 <p>To encrypt an email to Edward, you need his public key, so now you'll have
 578 Enigmail download it from a keyserver. Click Download Missing Keys and use
 579 the default in the pop-up that asks you to choose a keyserver. Once it finds
 580 keys, check the first one (Key ID starting with C), then select ok. Select
 581 ok in the next pop-up.</p>
 582
 583 <p>Now you are back at the "Recipients not valid, not trusted or not found"
 584 screen. Check the box in front of Edward's key and click Send.</p>
 585
 586 <p class="notes">Since you encrypted this email with Edward's public key,
 587 Edward's private key is required to decrypt it. Edward is the only one with
 588 his private key, so no one except him can decrypt it.</p>
 589
 590 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 591 <div class="troubleshooting">
 592
 593 <h4>Troubleshooting</h4>
 594
 595 <dl>
 596 <dt>Enigmail can't find Edward's key</dt>
 597 <dd>Close the pop-ups that have appeared since you clicked Send. Make sure
 598 you are connected to the Internet and try again. If that doesn't work, repeat
 599 the process, choosing a different keyserver when it asks you to pick one.</dd>
 600
 601 <dt>Unscrambled messages in the Sent folder</dt>
 602 <dd>Even though you can't decrypt messages encrypted to someone else's key,
 603 your email program will automatically save a copy encrypted to your public key,
 604 which you'll be able to view from the Sent folder like a normal email. This
 605 is normal, and it doesn't mean that your email was not sent encrypted.</dd>
 606
 607 <dt>More resources</dt>
 608 <dd>If you're still having trouble with our
 609 instructions or just want to learn more, check out <a
 610 href="https://www.enigmail.net/documentation/Signature_and_Encryption#Encrypting_a_message">
 611 Enigmail's wiki</a>.</dd>
 612
 613 <dt class="feedback">Don't see a solution to your problem?</dt>
 614 <dd class="feedback">Please let us know on the <a
 615 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 616 page</a>.</dd>
 617 </dl>
 618
 619 </div><!-- /.troubleshooting -->
 620
 621 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 622 <div class="troubleshooting">
 623
 624 <h4>Advanced</h4>
 625
 626 <dl>
 627 <dt>Encrypt messages from the command line</dt>
 628 <dd>You can also encrypt and decrypt messages and files from the <a
 629 href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>,
 630 if that's your preference. The option --armor makes the encrypted output
 631 appear in the regular character set.</dd>
 632 </dl>
 633
 634 </div><!-- /.troubleshooting -->
 635 </div><!-- End .main -->
 636 </div><!-- End #step-3b .step -->
 637
 638 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 639 <div id="step-headers_unencrypted" class="step">
 640 <div class="main">
 641
 642 <h3><em>Important:</em> Security tips</h3>
 643
 644 <p>Even if you encrypt your email, the subject line is not encrypted, so
 645 don't put private information there. The sending and receiving addresses
 646 aren't encrypted either, so a surveillance system can still figure out who
 647 you're communicating with. Also, surveillance agents will know that you're
 648 using GnuPG, even if they can't figure out what you're saying. When you
 649 send attachments, Enigmail will give you the choice to encrypt them or not,
 650 independent of the actual email.</p>
 651
 652 <p>For greater security against potential attacks, you can turn off
 653 HTML. Instead, you can render the message body as plain text.</p>
 654
 655 </div><!-- End .main -->
 656 </div><!-- End #step-headers_unencrypted .step-->
 657
 658 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 659 <div id="step-3c" class="step">
 660 <div class="main">
 661
 662 <h3><em>Step 3.c</em> Receive a response</h3>
 663
 664 <p>When Edward receives your email, he will use his private key to decrypt
 665 it, then 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 </div><!-- End .main -->
 672 </div><!-- End #step-3c .step -->
 673
 674 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 675 <div id="step-3d" class="step">
 676 <div class="main">
 677
 678 <h3><em>Step 3.d</em> Send a test signed email</h3>
 679
 680 <p>GnuPG includes a way for you to sign messages and files, verifying that
 681 they came from you and that they weren't tampered with along the way. These
 682 signatures are stronger than their pen-and-paper cousins -- they're impossible
 683 to forge, because they're impossible to create without your private key
 684 (another reason to keep your private key safe).</p>
 685
 686 <p>You can sign messages to anyone, so it's a great way to make people
 687 aware that you use GnuPG and that they can communicate with you securely. If
 688 they don't have GnuPG, they will be able to read your message and see your
 689 signature. If they do have GnuPG, they'll also be able to verify that your
 690 signature is authentic.</p>
 691
 692 <p>To sign an email to Edward, compose any message to him and click the
 693 pencil icon next to the lock icon so that it turns gold. If you sign a
 694 message, GnuPG may ask you for your password before it sends the message,
 695 because it needs to unlock your private key for signing.</p>
 696
 697 <p>With the lock and pencil icons, you can choose whether each message will
 698 be encrypted, signed, both, or neither.</p>
 699
 700 </div>
 701 </div>
 702
 703 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 704 <div id="step-3e" class="step">
 705 <div class="main">
 706
 707 <h3><em>Step 3.e</em> Receive a response</h3>
 708
 709 <p>When Edward receives your email, he will use your public key (which
 710 you sent him in <a href="#step-3a">Step 3.A</a>) to verify the message
 711 you sent has not been tampered with and to encrypt his reply to you.</p>
 712
 713 <p class="notes">It may take two or three minutes for Edward to
 714 respond. In the meantime, you might want to skip ahead and check out the <a
 715 href="#section5">Use it Well</a> section of this guide.</p>
 716
 717 <p>Edward's reply will arrive encrypted, because he prefers to use encryption
 718 whenever possible. If everything goes according to plan, it should say
 719 "Your signature was verified." If your test signed email was also encrypted,
 720 he will mention that first.</p>
 721
 722 <p>When you receive Edward's email and open it, Enigmail will
 723 automatically detect that it is encrypted with your public key, and
 724 then it will use your private key to decrypt it.</p>
 725
 726 <p>Notice the bar that Enigmail shows you above the message, with
 727 information about the status of Edward's key.</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" value="xD41A008"
 797 name="FROM"></p>
 798
 799 <p><strong>To:</strong><input type="text" value="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 a shorter
 826 key ID. This key ID is visible directly from the Key Management
 827 window. These eight character key IDs were previously used for
 828 identification, which used to be safe, but is no longer reliable. You
 829 need to check the full fingerprint as part of verifying you have the
 830 correct key for the person you are trying to contact. Spoofing, in
 831 which someone intentionally generates a key with a fingerprint whose
 832 final eight characters are the same as another, is unfortunately
 833 common.</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/Key_Management">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">
1109 source 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
1142 <script type="text/javascript"
1143 src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
1144 <script type="text/javascript"
1145 src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
1146 <!-- Piwik -->
1147 <script type="text/javascript" ><!--
1148 // @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&amp;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>
1158 <noscript><p><img
1159 src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0"
1160 alt="" /></p></noscript>
1161 <!-- End Piwik Tracking Code -->
1162 </body>
1163 </html>