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