en/mac.html

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