en/index.html

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