en/index.html

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