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