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