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