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