en/index.html

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