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