en/index.html

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