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