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