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