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