en/index.html

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