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