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