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, 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><iframe src="//static.fsf.org/nosvn/banners/2021fundraiser-spring/" style="width: 100%; height: 150px; display: block; margin: 0; border: 0 none; overflow: hidden;"></iframe>
  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             <!-- Begin fsf-modal-window-elem campaign element -->
  24             <link type="text/css" rel="stylesheet" href="https://static.fsf.org/nosvn/fonts/fa/css/font-awesome.min.css">
  25             <style>
  26 #fsf-modal-window-elem-container div {
  27     -webkit-box-sizing: border-box;
  28        -moz-box-sizing: border-box;
  29             box-sizing: border-box;
  30 }
  31
  32 @media screen and (min-width: 700px) {
  33
  34     #fsf-modal-window-elem-outer-v-center {
  35         display: table;
  36         position: absolute;
  37         height: 100%;
  38         width: 100%;
  39     }
  40     #fsf-modal-window-elem-inner-v-center {
  41         display: table-cell;
  42         vertical-align: middle;
  43     }
  44
  45     #fsf-modal-window-elem {
  46         width: 687px;
  47         margin-left: auto;
  48         margin-right: auto;
  49     }
  50
  51     #fsf-modal-window-elem-right-column {
  52         float: right;
  53         width: 280px;
  54         padding-left: 20px;
  55         color: #491e17;
  56     }
  57
  58     #fsf-modal-window-elem-left-column {
  59         width: 100%;
  60         float: left;
  61         margin-right: -280px;
  62     }
  63
  64     #fsf-modal-window-elem-text {
  65         margin-right: 280px;
  66     }
  67 }
  68
  69 @media screen and (max-width: 699px) {
  70
  71     #fsf-modal-window-elem {
  72
  73         -ms-box-orient: horizontal;
  74         display: -webkit-box;
  75         display: -moz-box;
  76         display: -ms-flexbox;
  77         display: -moz-flex;
  78         display: -webkit-flex;
  79         display: flex;
  80
  81         -webkit-flex-flow: row wrap;
  82         flex-flow: row wrap;
  83     }
  84
  85     #fsf-modal-window-elem {
  86         width: 80vw;
  87         margin-left: 10vw;
  88         margin-right: 10vw;
  89         margin-top: 40px;
  90         margin-bottom: 40px;
  91     }
  92
  93     #fsf-modal-window-elem-right-column {
  94         width: 100%;
  95         order: 1;
  96     }
  97
  98     #fsf-modal-window-elem-left-column {
  99         width: 100%;
 100         order: 2;
 101     }
 102
 103     #fsf-modal-window-elem-text {
 104         margin-top: 20px;
 105     }
 106 }
 107
 108 @media screen and (max-width: 360px) {
 109     .long-button-text {
 110         font-size: 25px !important;
 111     }
 112 }
 113
 114 #fsf-modal-window-elem-container {
 115     position: fixed;
 116     z-index: 10000;
 117     left: 0;
 118     top: 0;
 119     width: 100%;
 120     height: 100%;
 121     overflow: auto;
 122     background-color: rgba(0,0,0,0.8);
 123
 124     font-weight: normal;
 125 }
 126
 127 #fsf-modal-window-elem a, a:active, a:focus {
 128     outline: none;
 129     border-bottom: 0px;
 130 }
 131
 132 #fsf-modal-window-elem {
 133     overflow: auto;
 134     padding: 20px;
 135     border-style: solid;
 136     border-width: 5px;
 137     border-color: #3a5b2c;
 138     border-radius: 20px;
 139     box-shadow: 0px 0px 10px #111111;
 140     background-color: #fdf7b9;
 141 }
 142
 143 #fsf-modal-window-elem-header {
 144     width: 100%;
 145 }
 146
 147 #fsf-modal-window-elem-header h2 {
 148     font-family: sans-serif,"Helvetica",Arial;
 149     font-weight: bold;
 150     font-size: 24px;
 151     color: #002047;
 152     /* text-shadow: 0px 0px 8px #00378c; */
 153     padding-bottom: 20px;
 154     margin-top: 0px;
 155     margin-bottom: 0px;
 156     border: none;
 157 }
 158
 159 #fsf-modal-window-elem-close-button {
 160     float: right;
 161     height: 40px;
 162     margin-right: -20px;
 163     margin-top: -20px;
 164     padding: 11px;
 165     color: #888;
 166     cursor: pointer;
 167 }
 168
 169 #fsf-modal-window-elem-close-button:hover {
 170     color: #aaf;
 171 }
 172
 173 #fsf-modal-window-elem-right-column {
 174     text-align: center;
 175     -webkit-user-select: none;
 176        -moz-user-select: none;
 177         -ms-user-select: none;
 178             user-select: none;
 179 }
 180
 181 #fsf-modal-window-elem-buttons div {
 182     height:53.333px;
 183     line-height: 53.333px;
 184     margin-left:auto;
 185     margin-right:auto;
 186     display:block;
 187 }
 188
 189 #fsf-modal-window-elem-buttons {
 190 }
 191
 192 #fsf-modal-window-elem-buttons a {
 193     width: 100%;
 194     display: block;
 195     text-align: center;
 196     font-size:35px;
 197     color:#002047;
 198     text-decoration: none;
 199     font-family: sans-serif,"Helvetica",Arial;
 200     font-weight: normal;
 201 }
 202
 203 #fsf-modal-window-elem-maybe-later {
 204     margin-top: 5px;
 205     margin-bottom: -5px;
 206 }
 207
 208 #fsf-modal-window-elem-maybe-later a {
 209     color: #367c93;
 210     line-height: 20px;
 211     text-decoration: none;
 212     cursor: pointer;
 213     font-weight: normal;
 214     font-family: sans-serif,"Helvetica",Arial;
 215     font-size: 16px;
 216 }
 217
 218 #fsf-modal-window-elem-text {
 219 }
 220
 221 #fsf-modal-window-elem-text a {
 222     color: #002047;
 223     font-weight: 700;
 224     text-decoration: none;
 225 }
 226
 227 #fsf-modal-window-elem-text a:hover {
 228     color: #fd8e1b;
 229 }
 230
 231 #fsf-modal-window-elem-text a:focus {
 232     color: #fd8e1b;
 233 }
 234
 235 #fsf-modal-window-elem-text a:active {
 236     color: #ffac30;
 237 }
 238
 239 #fsf-modal-window-elem-text p {
 240     font-family: sans-serif,"Helvetica",Arial;
 241     font-size: 17px;
 242     font-weight: normal;
 243     margin: 0px 0px 10px 0px;
 244     line-height: 20px;
 245     color: #002047;
 246     /* text-shadow: 0px 0px 8px #004067;*/
 247 }
 248             </style>
 249             <div id="fsf-modal-window-elem-container" style="display: none;">
 250                 <div id="fsf-modal-window-elem-outer-v-center">
 251                     <div id="fsf-modal-window-elem-inner-v-center">
 252                         <div id="fsf-modal-window-elem">
 253                             <div id="fsf-modal-window-elem-header">
 254                                 <div id="fsf-modal-window-elem-close-button" onclick="//fsfModalWindowElemDontShowForAWhile();">
 255                                     <i class="fa fa-close">&#8203;</i>
 256                                 </div>
 257                                 <h2>Move freedom forward with a donation to the FSF!</h2>
 258                             </div>
 259                             <div id="fsf-modal-window-elem-left-column">
 260                                 <div id="fsf-modal-window-elem-text">
 261
 262 <p>
 263
 264 Free software has become a vital global movement for user autonomy.
 265
 266 </p>
 267
 268 <p>
 269
 270 Without free software, we cannot and will not have a free society. <b>We rely on donations from people like you, who use and appreciate our work.</b> Fuel our journey forward, and help us reach our ultimate destination: full software freedom.
 271
 272 </p>
 273
 274 <p>
 275
 276 Support us with a donation today, and help us achieve our summer financial goal of USD 50,000 before July 16.
 277
 278 </p>
 279
 280 <p><span id="fsf-modal-window-text-link"><a href="https://www.fsf.org/appeal?mtm_campaign=summer21&mtm_kwd=learn-more&mtm_source=modal">Read more</a> | <a href="https://my.fsf.org/join?mtm_campaign=summer21&mtm_source=modal">Join</a></span></p>
 281
 282                                 </div>
 283                             </div>
 284                             <div id="fsf-modal-window-elem-right-column">
 285                                 <div id="fsf-modal-window-elem-buttons" style="border-radius: 20px; box-shadow: 0px 0px 5px #0c2b2b;">
 286                                     <div style="background-color:#8c9e1e; border-top-right-radius: 20px; border-top-left-radius: 20px;">
 287                                       <a style="text-shadow: 0px 0px 6px #d5e471;" href="https://my.fsf.org/join?mtm_campaign=summer21&mtm_source=modal" onclick="//fsfModalWindowElemFollowedLink();"><i class="fa fa-check-circle">&nbsp;</i>Join</a>
 288                                     </div>
 289
 290                                     <div style="background-color:#fdf7b9">
 291                                       <a href="https://my.fsf.org/renew?mtm_campaign=summer21&mtm_source=modal" onclick="//fsfModalWindowElemFollowedLink();"><i class="fa fa-refresh">&nbsp;</i>Renew</a>
 292                                     </div>
 293
 294                                     <div style="background-color:#3a5b2c; border-bottom-right-radius: 20px; border-bottom-left-radius: 20px; margin-bottom: 2px">
 295                                       <a style="text-shadow: 0px 0px 6px #c2d831;" href="https://my.fsf.org/donate?mtm_campaign=summer21&mtm_source=modal" onclick="//fsfModalWindowElemFollowedLink();"><i class="fa fa-money">&nbsp;</i>Donate</a>
 296                                     </div>
 297                                 </div>
 298                             </div>
 299                         </div>
 300                     </div>
 301                 </div>
 302                 <script>
 303 // @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-3.0
 304
 305 // Licensed GPLv3-or-later by Andrew Engelbrecht
 306
 307 var startTime, endTime, switchTextTime;
 308
 309 startTime = new Date('2021-06-15T04:00:00Z');
 310 switchTextTime = new Date('2021-08-17T04:00:00Z');
 311 // endTime is unused.
 312 endTime = new Date('2021-08-17T04:00:00Z');
 313
 314 // Possibly switch the text that is displayed in the modal window, depending
 315 // upon the current date.
 316 function fsfModalWindowElemMaybeSwitchText () {
 317
 318     var now;
 319
 320     now = new Date();
 321     if (now.getTime() < switchTextTime.getTime()) {
 322         return; // Do not switch the text
 323     }
 324
 325     // Switch text
 326     document.getElementById("fsf-modal-window-elem-text").innerHTML =' \
 327 \
 328 <p>Free software has become a vital global movement for user autonomy.<\/p><p>Without free software, we cannot and will not have a free society. <b>We rely on donations from people like you, who use and appreciate our work.<\/b> Fuel our journey forward, and help us reach our ultimate destination: full software freedom.<\/p><p>Support us with a donation today, and help us achieve our summer financial goal of USD 50,000 before July 16.<\/p> \
 329 \
 330 <p><span id="fsf-modal-window-text-link"><a href="https://www.fsf.org/appeal?mtm_campaign=summer21&mtm_kwd=learn-more&mtm_source=modal">Read more<\/a> |  <a href="https://my.fsf.org/join?mtm_campaign=summer21&mtm_source=modal">Join<\/a><\/span><\/p>';
 331 }
 332
 333 // Show fsf-modal-window-elem if it has not been previously closed by
 334 // the user, nor recently hit "maybe later",
 335 // and the campaign is still happening
 336 function fsfModalWindowElemMaybeShow () {
 337
 338     var pattern, noShowFsfModalWindowElementP, now;
 339
 340     // See if cookie says not to show element
 341     pattern = /showFsfSpring2021FundraiserModalWindowElementP\s*=\s*false/;
 342     noShowFsfModalWindowElementP = pattern.test(document.cookie);
 343
 344 //// Uncomment here to enable modal window hiding
 345     if (!noShowFsfModalWindowElementP) {
 346         setTimeout(function () {
 347             // display the element
 348             document.getElementById("fsf-modal-window-elem-container").style.display="block";
 349         }, 0);
 350     }
 351 }
 352
 353 // Call this first to set the proper text.
 354 fsfModalWindowElemMaybeSwitchText();
 355 // Check if appeal is the url.
 356 if (window.location.href.indexOf("appeal") == -1) {
 357   // Call this right away to avoid flicker.
 358   fsfModalWindowElemMaybeShow();
 359 }
 360
 361 // Get the time `plusDays` in the future.
 362 // This can be a fraction.
 363 function daysInFuture (plusDays) {
 364     var now, future;
 365
 366     now = new Date();
 367     future = new Date(now.getTime() + Math.floor(1000 * 60 * 60 * 24 * plusDays));
 368     return future.toGMTString();
 369 }
 370
 371 // Hide the fsf-modal-window-elem
 372 function fsfModalWindowElemHide () {
 373     document.getElementById("fsf-modal-window-elem-container").style.display="none";
 374 }
 375
 376 // Optionally hide elem and set a cookie to keep the fsf-modal-window-elem hidden for the next `forDays`.
 377 function fsfModalWindowElemDontShowForDays (forDays, hideNow) {
 378     if (hideNow === true) {
 379         fsfModalWindowElemHide();
 380     }
 381     //document.cookie = "showFsfSpring2021FundraiserModalWindowElementP=false; path=/; domain=.fsf.org; expires=" + daysInFuture(forDays);
 382     document.cookie = "showFsfSpring2021FundraiserModalWindowElementP=false; path=/; SameSite=Strict; Secure; expires=" + daysInFuture(forDays);
 383 }
 384
 385 // Hide the element from now to two weeks after closing it
 386 function fsfModalWindowElemDontShowForAWhile () {
 387     fsfModalWindowElemDontShowForDays(7, true);
 388 }
 389
 390 // Keep the element visible for now, but do not show it for a while
 391 function fsfModalWindowElemFollowedLink () {
 392     fsfModalWindowElemDontShowForDays(14, false);
 393 }
 394
 395 // Check if visiting appeal page.
 396 if (window.location.href.indexOf("appeal") > -1) {
 397   fsfModalWindowElemDontShowForAWhile();
 398 }
 399
 400 // Close popup if user clicks trasparent part
 401 document.getElementById("fsf-modal-window-elem-container").addEventListener("click", function(event){
 402     fsfModalWindowElemDontShowForAWhile();
 403 });
 404
 405 // Do not close popup if clicking non-trasparent part (with the text and buttons)
 406 document.getElementById("fsf-modal-window-elem").addEventListener("click", function(event){
 407     event.stopPropagation();
 408 });
 409
 410 // Close popup if user clicks X icon
 411 document.getElementById("fsf-modal-window-elem-close-button").addEventListener("click", function(event){
 412     fsfModalWindowElemDontShowForAWhile();
 413 });
 414
 415 // Disable popup if user clicks one of the main buttons
 416 document.getElementById("fsf-modal-window-elem-buttons").addEventListener("click", function(event){
 417     fsfModalWindowElemFollowedLink();
 418 });
 419
 420 // Disable popup if user clicks one of the "Read more" link
 421 document.getElementById("fsf-modal-window-text-link").addEventListener("click", function(event){
 422     fsfModalWindowElemFollowedLink();
 423 });
 424
 425 // Close popup if user presses escape key
 426 window.addEventListener("keydown",  function  (event)  {
 427     switch  (event.key)  {
 428         case  "Escape":
 429             fsfModalWindowElemDontShowForAWhile();
 430             break;
 431         default:
 432             return;
 433     }
 434 },  true);
 435 // @license-end
 436                 </script>
 437             </div>
 438             <!-- End fsf-modal-window-elem campaign element -->
 439
 440 <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
 441 <header class="row" id="header"><div>
 442
 443
 444 <h1>Email Self-Defense</h1>
 445
 446 <!-- Language list for browsers that do not have JS enabled -->
 447 <ul id="languages" class="os">
 448 <li><a class="current" href="/en">English - v4.0</a></li>
 449 <li><a href="/cs">čeština - v4.0</a></li>
 450 <li><a href="/de">Deutsch - v4.0</a></li>
 451 <li><a href="/el">ελληνικά - v3.0</a></li>
 452 <li><a href="/es">español - v4.0</a></li>
 453 <li><a href="/fa">فارسی - v4.0</a></li>
 454 <li><a href="/fr">français - v4.0</a></li>
 455 <li><a href="/it">italiano - v3.0</a></li>
 456 <li><a href="/ja">日本語 - v4.0</a></li>
 457 <li><a href="/pt-br">português do Brasil - v3.0</a></li>
 458 <li><a href="/ro">română - v3.0</a></li>
 459 <li><a href="/ru">русский - v4.0</a></li>
 460 <li><a href="/sq">Shqip - v4.0</a></li>
 461 <li><a href="/sv">svenska - v4.0</a></li>
 462 <li><a href="/tr">Türkçe - v4.0</a></li>
 463 <li><a href="/zh-hans">简体中文 - v4.0</a></li>
 464 <li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
 465 <strong><span style="color: #2F5FAA;">Translate!</span></strong></a></li>
 466 </ul>
 467
 468 <ul id="menu" class="os">
 469 <li class="spacer"><a href="index.html" class="current">GNU/Linux</a></li>
 470 <li><a href="mac.html">Mac OS</a></li>
 471 <li><a href="windows.html">Windows</a></li>
 472 <li class="spacer"><a href="workshops.html">Teach your friends</a></li>
 473 <li class="spacer"><a
 474 href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email encryption for everyone via %40fsf">
 475 Share&nbsp;
 476 <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class="share-logo"
 477 alt="[GNU Social]" />&nbsp;
 478 <img src="//static.fsf.org/nosvn/enc-dev0/img/mastodon.png" class="share-logo"
 479 alt="[Mastodon]" />&nbsp;
 480 <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" class="share-logo"
 481 alt="[Reddit]" />&nbsp;
 482 <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" class="share-logo"
 483 alt="[Hacker News]" /></a></li>
 484 </ul>
 485
 486 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
 487 <div id="fsf-intro">
 488
 489 <h3><a href="http://u.fsf.org/ys"><img
 490 alt="Free Software Foundation"
 491 src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
 492 </a></h3>
 493
 494 <div class="fsf-emphasis">
 495
 496 <p>We fight for computer users' rights, and promote the development of free (as
 497 in freedom) software. Resisting bulk surveillance is very important to us.</p>
 498
 499 <p><strong>Please donate to support Email Self-Defense. We need to keep
 500 improving it, and making more materials, for the benefit of people around
 501 the world taking the first step towards protecting their privacy.</strong></p>
 502
 503 </div>
 504
 505 <p><a
 506 href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&amp;id=14&amp;pk_campaign=email_self_defense&amp;mtm_kwd=guide_donate"><img
 507 alt="Donate"
 508 src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a></p>
 509
 510 </div><!-- End #fsf-intro -->
 511
 512 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
 513 <div class="intro">
 514
 515 <p><a id="infographic" href="infographic.html"><img
 516 src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png"
 517 alt="View &amp; share our infographic &rarr;" /></a>
 518 Bulk surveillance violates our fundamental rights and makes free speech
 519 risky. This guide will teach you a basic surveillance self-defense skill: email
 520 encryption. Once you've finished, you'll be able to send and receive emails
 521 that are scrambled to make sure a surveillance agent or thief intercepting
 522 your email can't read them. All you need is a computer with an Internet
 523 connection, an email account, and about forty minutes.</p>
 524
 525 <p>Even if you have nothing to hide, using encryption helps protect the privacy
 526 of people you communicate with, and makes life difficult for bulk surveillance
 527 systems. If you do have something important to hide, you're in good company;
 528 these are the same tools that whistleblowers use to protect their identities
 529 while shining light on human rights abuses, corruption and other crimes.</p>
 530
 531 <p>In addition to using encryption, standing up
 532 to surveillance requires fighting politically for a <a
 533 href="https://gnu.org/philosophy/surveillance-vs-democracy.html">reduction
 534 in the amount of data collected on us</a>, but the essential first step is
 535 to protect yourself and make surveillance of your communication as difficult
 536 as possible. This guide helps you do that. It is designed for beginners, but
 537 if you already know the basics of GnuPG or are an experienced free software
 538 user, you'll enjoy the advanced tips and the <a href="workshops.html">guide
 539 to teaching your friends</a>.</p>
 540
 541 </div><!-- End .intro -->
 542 </div></header><!-- End #header -->
 543
 544 <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
 545 <section class="row" id="section1"><div>
 546
 547 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 548 <div class="section-intro">
 549
 550 <h2><em>#1</em> Get the pieces</h2>
 551
 552 <p class="notes">This guide relies on software which is <a
 553 href="https://www.gnu.org/philosophy/free-sw.html">freely licensed</a>;
 554 it's completely transparent and anyone can copy it or make their
 555 own version. This makes it safer from surveillance than proprietary
 556 software (like Windows or Mac OS). Learn more about free software at <a
 557 href="https://u.fsf.org/ys">fsf.org</a>.</p>
 558
 559 <p>Most GNU/Linux operating systems come with GnuPG installed on them,
 560 so you don't have to download it. Before configuring your encryption setup with this guide, though, you'll need a desktop email program based on Thunderbird installed on your computer. Many GNU/Linux distributions have Thunderbird installed already. If you're using a [fully free distribution of GNU/Linux](https://www.gnu.org/distros/free-distros.html), we recommend installing "Icedove" instead. 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>
 561
 562 <p>If you already have an email program, you can skip to <a
 563 href="#step-1b">Step 1.b</a>.</p>
 564
 565 </div><!-- End .section-intro -->
 566
 567 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 568 <div id="step-1a" class="step">
 569 <div class="sidebar">
 570
 571 <p><img
 572 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png"
 573 alt="Step 1.A: Install Wizard" /></p>
 574
 575 </div><!-- /.sidebar -->
 576 <div class="main">
 577
 578 <h3><em>Step 1.a</em> Set up your email program with your email account</h3>
 579
 580 <p>Open your email program and follow the wizard (step-by-step walkthrough)
 581 that sets it up with your email account.</p>
 582
 583 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 584 <div class="troubleshooting">
 585
 586 <h4>Troubleshooting</h4>
 587
 588 <dl>
 589 <dt>The wizard doesn't launch</dt>
 590 <dd>You can launch the wizard yourself, but the menu option for doing so is
 591 named differently in each email program. The button to launch it will be in
 592 the program's main menu, under "New" or something similar, titled something
 593 like "Add account" or "New/Existing email account."</dd>
 594
 595 <dt>The wizard can't find my account or isn't downloading my mail</dt>
 596 <dd>Before searching the Web, we recommend you start by asking other people
 597 who use your email system, to figure out the correct settings.</dd>
 598
 599 <dt class="feedback">Don't see a solution to your problem?</dt>
 600 <dd class="feedback">Please let us know on the <a
 601 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 602 page</a>.</dd>
 603 </dl>
 604
 605 </div><!-- /.troubleshooting -->
 606 </div><!-- End .main -->
 607 </div><!-- End #step1-a .step -->
 608
 609 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 610 <div id="step-1b" class="step">
 611 <div class="sidebar">
 612 <ul class="images">
 613 <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png"
 614 alt="Step 1.B: Tools -> Add-ons" /></li>
 615 <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png"
 616 alt="Step 1.B: Search Add-ons" /></li>
 617 <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png"
 618 alt="Step 1.B: Install Add-ons" /></li>
 619 </ul>
 620
 621 </div><!-- /.sidebar -->
 622 <div class="main">
 623
 624 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 625 <div class="troubleshooting">
 626
 627 <h4>Troubleshooting</h4>
 628
 629 <dl>
 630 <dt>I can't find the menu.</dt>
 631 <dd>In many new email programs, the main menu is represented by an image of
 632 three stacked horizontal bars.</dd>
 633
 634 <dt class="feedback">Don't see a solution to your problem?</dt>
 635 <dd class="feedback">Please let us know on the <a
 636 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 637 page</a>.</dd>
 638 </dl>
 639
 640 </div><!-- /.troubleshooting -->
 641 </div><!-- End .main -->
 642 </div><!-- End #step-1b .step -->
 643 </div></section><!-- End #section1 -->
 644
 645 <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
 646 <section class="row" id="section2"><div>
 647
 648 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 649 <div class="section-intro">
 650
 651 <h2><em>#2</em> Make your keys</h2>
 652
 653 <p>To use the GnuPG system, you'll need a public key and a private key (known
 654 together as a keypair). Each is a long string of randomly generated numbers
 655 and letters that are unique to you. Your public and private keys are linked
 656 together by a special mathematical function.</p>
 657
 658 <p>Your public key isn't like a physical key, because it's stored in the open
 659 in an online directory called a keyserver. People download it and use it,
 660 along with GnuPG, to encrypt emails they send to you. You can think of the
 661 keyserver as a phonebook; people who want to send you encrypted email can
 662 look up your public key.</p>
 663
 664 <p>Your private key is more like a physical key, because you keep it to
 665 yourself (on your computer). You use GnuPG and your private key together to
 666 descramble encrypted emails other people send to you. <span style="font-weight:
 667 bold;">You should never share your private key with anyone, under any
 668 circumstances.</span></p>
 669
 670 <p>In addition to encryption and decryption, you can also use these keys to
 671 sign messages and check the authenticity of other people's signatures. We'll
 672 discuss this more in the next section.</p>
 673
 674 </div><!-- End .section-intro -->
 675
 676 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 677 <div id="step-2a" class="step">
 678 <div class="sidebar">
 679
 680 <p><img
 681 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png"
 682 alt="Step 2.A: Make a Keypair" /></p>
 683
 684 </div><!-- /.sidebar -->
 685 <div class="main">
 686
 687 <h3><em>Step 2.a</em> Make a keypair</h3>
 688
 689 <p>We will use the command line to create a keypair using the gnupg program. This should be installed on your Gnu/Linux operating system.
 690 Open a terminal using <text style= "color:#2f5faa">ctrl + alt + t</text> and use the following code to create your keypair:</p>
 691
 692 <p><text style="color:#2f5faa">gpg --full-generate-key</text> to start the process.</p>
 693 <p>To answer what kind of key you would like to create, select the default option <text style="color:#2f5faa"> 1 RSA and RSA<text>.</p>
 694 <p>Enter the following keysize: <text style="color:#2f5faa">4096</text></p>
 695 <p>Choose the expiration date, we suggest <text style="color:#2f5faa">2y</text>.</p>
 696 <p>Follow the prompts to continue setting up with your personal details.</p>
 697
 698 <img src="create-key.png">
 699
 700 - What does RSA mean -
 701 - Why the 4096 keysize -
 702
 703 <li>On the screen titled "Passphrase," pick a strong password! You can
 704 do it manually, or you can use the Diceware method. Doing it manually
 705 is faster but not as secure. Using Diceware takes longer and requires
 706 dice, but creates a password that is much harder for attackers to figure
 707 out. To use it, read the section "Make a secure passphrase with Diceware" in <a
 708 href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">
 709 this article</a> by Micah Lee.</li>
 710 </ul>
 711
 712 <p>If you'd like to pick a password manually, come up with something
 713 you can remember which is at least twelve characters long, and includes
 714 at least one lower case and upper case letter and at least one number or
 715 punctuation symbol. Never pick a password you've used elsewhere. Don't use
 716 any recognizable patterns, such as birthdays, telephone numbers, pets' names,
 717 song lyrics, quotes from books, and so on.</p>
 718
 719
 720
 721 <p><span style="font-weight: bold;">When the "Key Generation Completed" screen
 722 pops up, select Generate Certificate and choose to save it in a safe place on
 723 your computer (we recommend making a folder called "Revocation Certificate"
 724 in your home folder and keeping it there). This step is essential for your
 725 email self-defense, as you'll learn more about in <a href="#section5">Section
 726 5</a>.</span></p>
 727
 728 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 729 <div class="troubleshooting">
 730
 731 <h4>Troubleshooting</h4>
 732
 733 <dl>
 734 <dt>GnuPG is not installed</dt>
 735 <dd><p class = "notes">
 736   <p>GPG is not installed. You can check if this is the case with
 737   <p>gnupg --version
 738   <p>If Gnupg is not installed, it would bring up the following result:
 739   <p>Command 'gpg' not found, but can be installed with:
 740   sudo apt install gnupg
 741   <p>Then follow that command and install the program:
 742   sudo apt install gnupg gnupg2</p></dd>
 743
 744 <dt>I can't find the Enigmail menu.</dt>
 745 <dd>In many new email programs, the main menu is represented by an image
 746 of three stacked horizontal bars. Enigmail may be inside a section called
 747 Tools.</dd>
 748
 749 <dt>The wizard says that it cannot find GnuPG.</dt>
 750 <dd>Open whatever program you usually use for installing software, and search
 751 for GnuPG, then install it. Then restart the Enigmail setup wizard by going
 752 to Enigmail &rarr; Setup Wizard.</dd>
 753
 754 <dt>More resources</dt>
 755 <dd>If you're having trouble with our
 756 instructions or just want to learn more, check out <a
 757 href="https://www.enigmail.net/documentation/Key_Management#Generating_your_own_key_pair">
 758 Enigmail's wiki instructions for key generation</a>.</dd>
 759
 760 <dt class="feedback">Don't see a solution to your problem?</dt>
 761 <dd class="feedback">Please let us know on the <a
 762 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 763 page</a>.</dd>
 764 </dl>
 765
 766 </div><!-- /.troubleshooting -->
 767
 768 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 769 <div class="troubleshooting">
 770
 771 <h4>Advanced</h4>
 772
 773 <dl>
 774 <dt>Command line key generation</dt>
 775 <dd>If you prefer using the command line for a higher
 776 degree of control, you can follow the documentation from <a
 777 href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy
 778 Handbook</a>. Make sure you stick with "RSA and RSA" (the default),
 779 because it's newer and more secure than the algorithms the documentation
 780 recommends. Also make sure your key is at least 2048 bits, or 4096 if you
 781 want to be extra secure.</dd>
 782
 783 <dt>Advanced key pairs</dt>
 784 <dd>When GnuPG creates a new keypair, it compartmentalizes
 785 the encryption function from the signing function through <a
 786 href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use
 787 subkeys carefully, you can keep your GnuPG identity much more
 788 secure and recover from a compromised key much more quickly. <a
 789 href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a>
 790 and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a>
 791 provide good guides for setting up a secure subkey configuration.</dd>
 792 </dl>
 793
 794 </div><!-- /.troubleshooting -->
 795 </div><!-- End .main -->
 796 </div><!-- End #step-2a .step -->
 797
 798 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 799 <div id="step-2b" class="step">
 800 <div class="main">
 801
 802 <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
 803
 804 <p>In your email program's menu, select Enigmail &rarr; Key Management.</p>
 805
 806 <p>Right click on your key and select Upload Public Keys to Keyserver. You
 807 don't have to use the default keyserver. If, after research, you would like
 808 to change to a different default keyserver, you can change that setting
 809 manually in the Enigmail preferences.</p>
 810
 811 <p class="notes">Now someone who wants to send you an encrypted message can
 812 download your public key from the Internet. There are multiple keyservers
 813 that you can select from the menu when you upload, but they are all copies
 814 of each other, so it doesn't matter which one you use. However, it sometimes
 815 takes a few hours for them to match each other when a new key is uploaded.</p>
 816
 817 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 818 <div class="troubleshooting">
 819
 820 <h4>Troubleshooting</h4>
 821
 822 <dl>
 823 <dt>The progress bar never finishes</dt>
 824 <dd>Close the upload popup, make sure you are connected to the Internet,
 825 and try again. If that doesn't work, try again, selecting a different
 826 keyserver.</dd>
 827
 828 <dt>My key doesn't appear in the list</dt>
 829 <dd>Try checking "Display All Keys by Default."</dd>
 830
 831 <dt>More documentation</dt>
 832 <dd>If you're having trouble with our
 833 instructions or just want to learn more, check out <a
 834 href="https://www.enigmail.net/documentation/Key_Management#Distributing_your_public_key">
 835 Enigmail's documentation</a>.</dd>
 836
 837 <dt class="feedback">Don't see a solution to your problem?</dt>
 838 <dd class="feedback">Please let us know on the <a
 839 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 840 page</a>.</dd>
 841 </dl>
 842
 843 </div><!-- /.troubleshooting -->
 844
 845 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 846 <div class="troubleshooting">
 847
 848 <h4>Advanced</h4>
 849
 850 <dl>
 851 <dt>Uploading a key from the command line</dt>
 852 <dd>You can also upload your keys to a keyserver through the <a
 853 href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a
 854 href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a>
 855 maintains a list of highly interconnected keyservers. You can also <a
 856 href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export
 857 your key</a> as a file on your computer.</dd>
 858 </dl>
 859
 860 </div><!-- /.troubleshooting -->
 861 </div><!-- End .main -->
 862 </div><!-- End #step-2b .step -->
 863
 864 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 865 <div id="terminology" class="step">
 866 <div class="main">
 867
 868 <h3>GnuPG, OpenPGP, what?</h3>
 869
 870 <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP
 871 are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the
 872 encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG)
 873 is the program that implements the standard. Enigmail is a plug-in program
 874 for your email program that provides an interface for GnuPG.</p>
 875
 876 </div><!-- End .main -->
 877 </div><!-- End #terminology.step-->
 878 </div></section><!-- End #section2 -->
 879
 880 <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
 881 <section class="row" id="section3"><div>
 882
 883 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 884 <div class="section-intro">
 885
 886 <h2><em>#3</em> Try it out!</h2>
 887
 888 <p>Now you'll try a test correspondence with a computer program named Edward,
 889 who knows how to use encryption. Except where noted, these are the same
 890 steps you'd follow when corresponding with a real, live person.</p>
 891
 892 <!-- <p>NOTE: Edward is currently having some technical difficulties, so he
 893 may take a long time to respond, or not respond at all. We're sorry about
 894 this and we're working hard to fix it. Your key will still work even without
 895 testing with Edward.</p> -->
 896 </div><!-- End .section-intro -->
 897
 898 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 899 <div id="step-3a" class="step">
 900 <div class="sidebar">
 901
 902 <p><img
 903 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png"
 904 alt="Try it out." /></p>
 905
 906 </div><!-- /.sidebar -->
 907 <div class="main">
 908
 909 <h3><em>Step 3.a</em> Send Edward your public key</h3>
 910
 911 <p>This is a special step that you won't have to do when corresponding
 912 with real people. In your email program's menu, go to Enigmail &rarr; Key
 913 Management. You should see your key in the list that pops up. Right click
 914 on your key and select Send Public Keys by Email. This will create a new
 915 draft message, as if you had just hit the Write button.</p>
 916
 917 <p>Address the message to <a
 918 href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word
 919 (whatever you want) in the subject and body of the email. Don't send yet.</p>
 920
 921 <p>The lock icon in the top left should be yellow, meaning encryption is
 922 turned on. We want this first special message to be unencrypted, so
 923 click the icon once to turn it off. The lock should become grey, with a
 924 blue dot on it (to alert you that the setting has been changed from the
 925 default). Once encryption is off, hit Send.</p>
 926
 927 <p class="notes">It may take two or three minutes for Edward to
 928 respond. In the meantime, you might want to skip ahead and check out the <a
 929 href="#section5">Use it Well</a> section of this guide. Once he's responded,
 930 head to the next step. From here on, you'll be doing just the same thing as
 931 when corresponding with a real person.</p>
 932
 933 <p>When you open Edward's reply, GnuPG may prompt you for your password
 934 before using your private key to decrypt it.</p>
 935
 936 </div><!-- End .main -->
 937 </div><!-- End #step-3a .step -->
 938
 939 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
 940 <div id="step-3b" class="step">
 941 <div class="main">
 942
 943 <h3><em>Step 3.b</em> Send a test encrypted email</h3>
 944
 945 <p>Write a new email in your email program, addressed to <a
 946 href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject
 947 "Encryption test" or something similar and write something in the body.</p>
 948
 949 <p>The lock icon in the top left of the window should be yellow, meaning
 950 encryption is on. This will be your default from now on.</p>
 951
 952 <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll
 953 get to this in a moment.</p>
 954
 955 <p>Click Send. Enigmail will pop up a window that says "Recipients not valid,
 956 not trusted or not found."</p>
 957
 958 <p>To encrypt an email to Edward, you need his public key, so now you'll have
 959 Enigmail download it from a keyserver. Click Download Missing Keys and use
 960 the default in the pop-up that asks you to choose a keyserver. Once it finds
 961 keys, check the first one (Key ID starting with C), then select ok. Select
 962 ok in the next pop-up.</p>
 963
 964 <p>Now you are back at the "Recipients not valid, not trusted or not found"
 965 screen. Check the box in front of Edward's key and click Send.</p>
 966
 967 <p class="notes">Since you encrypted this email with Edward's public key,
 968 Edward's private key is required to decrypt it. Edward is the only one with
 969 his private key, so no one except him can decrypt it.</p>
 970
 971 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
 972 <div class="troubleshooting">
 973
 974 <h4>Troubleshooting</h4>
 975
 976 <dl>
 977 <dt>Enigmail can't find Edward's key</dt>
 978 <dd>Close the pop-ups that have appeared since you clicked Send. Make sure
 979 you are connected to the Internet and try again. If that doesn't work, repeat
 980 the process, choosing a different keyserver when it asks you to pick one.</dd>
 981
 982 <dt>Unscrambled messages in the Sent folder</dt>
 983 <dd>Even though you can't decrypt messages encrypted to someone else's key,
 984 your email program will automatically save a copy encrypted to your public key,
 985 which you'll be able to view from the Sent folder like a normal email. This
 986 is normal, and it doesn't mean that your email was not sent encrypted.</dd>
 987
 988 <dt>More resources</dt>
 989 <dd>If you're still having trouble with our
 990 instructions or just want to learn more, check out <a
 991 href="https://www.enigmail.net/documentation/Signature_and_Encryption#Encrypting_a_message">
 992 Enigmail's wiki</a>.</dd>
 993
 994 <dt class="feedback">Don't see a solution to your problem?</dt>
 995 <dd class="feedback">Please let us know on the <a
 996 href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
 997 page</a>.</dd>
 998 </dl>
 999
1000 </div><!-- /.troubleshooting -->
1001
1002 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
1003 <div class="troubleshooting">
1004
1005 <h4>Advanced</h4>
1006
1007 <dl>
1008 <dt>Encrypt messages from the command line</dt>
1009 <dd>You can also encrypt and decrypt messages and files from the <a
1010 href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>,
1011 if that's your preference. The option --armor makes the encrypted output
1012 appear in the regular character set.</dd>
1013 </dl>
1014
1015 </div><!-- /.troubleshooting -->
1016 </div><!-- End .main -->
1017 </div><!-- End #step-3b .step -->
1018
1019 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1020 <div id="step-headers_unencrypted" class="step">
1021 <div class="main">
1022
1023 <h3><em>Important:</em> Security tips</h3>
1024
1025 <p>Even if you encrypt your email, the subject line is not encrypted, so
1026 don't put private information there. The sending and receiving addresses
1027 aren't encrypted either, so a surveillance system can still figure out who
1028 you're communicating with. Also, surveillance agents will know that you're
1029 using GnuPG, even if they can't figure out what you're saying. When you
1030 send attachments, Enigmail will give you the choice to encrypt them or not,
1031 independent of the actual email.</p>
1032
1033 <p>For greater security against potential attacks, you can turn off
1034 HTML. Instead, you can render the message body as plain text. In order
1035 to do this in Thunderbird, go to View &gt; Message Body As &gt; Plain
1036 Text.</p>
1037
1038 </div><!-- End .main -->
1039 </div><!-- End #step-headers_unencrypted .step-->
1040
1041 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1042 <div id="step-3c" class="step">
1043 <div class="main">
1044
1045 <h3><em>Step 3.c</em> Receive a response</h3>
1046
1047 <p>When Edward receives your email, he will use his private key to decrypt
1048 it, then reply to you. </p>
1049
1050 <p class="notes">It may take two or three minutes for Edward to
1051 respond. In the meantime, you might want to skip ahead and check out the <a
1052 href="#section5">Use it Well</a> section of this guide.</p>
1053
1054 </div><!-- End .main -->
1055 </div><!-- End #step-3c .step -->
1056
1057 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1058 <div id="step-3d" class="step">
1059 <div class="main">
1060
1061 <h3><em>Step 3.d</em> Send a test signed email</h3>
1062
1063 <p>GnuPG includes a way for you to sign messages and files, verifying that
1064 they came from you and that they weren't tampered with along the way. These
1065 signatures are stronger than their pen-and-paper cousins -- they're impossible
1066 to forge, because they're impossible to create without your private key
1067 (another reason to keep your private key safe).</p>
1068
1069 <p>You can sign messages to anyone, so it's a great way to make people
1070 aware that you use GnuPG and that they can communicate with you securely. If
1071 they don't have GnuPG, they will be able to read your message and see your
1072 signature. If they do have GnuPG, they'll also be able to verify that your
1073 signature is authentic.</p>
1074
1075 <p>To sign an email to Edward, compose any message to him and click the
1076 pencil icon next to the lock icon so that it turns gold. If you sign a
1077 message, GnuPG may ask you for your password before it sends the message,
1078 because it needs to unlock your private key for signing.</p>
1079
1080 <p>With the lock and pencil icons, you can choose whether each message will
1081 be encrypted, signed, both, or neither.</p>
1082
1083 </div>
1084 </div>
1085
1086 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1087 <div id="step-3e" class="step">
1088 <div class="main">
1089
1090 <h3><em>Step 3.e</em> Receive a response</h3>
1091
1092 <p>When Edward receives your email, he will use your public key (which
1093 you sent him in <a href="#step-3a">Step 3.A</a>) to verify the message
1094 you sent has not been tampered with and to encrypt his reply to you.</p>
1095
1096 <p class="notes">It may take two or three minutes for Edward to
1097 respond. In the meantime, you might want to skip ahead and check out the <a
1098 href="#section5">Use it Well</a> section of this guide.</p>
1099
1100 <p>Edward's reply will arrive encrypted, because he prefers to use encryption
1101 whenever possible. If everything goes according to plan, it should say
1102 "Your signature was verified." If your test signed email was also encrypted,
1103 he will mention that first.</p>
1104
1105 <p>When you receive Edward's email and open it, Enigmail will
1106 automatically detect that it is encrypted with your public key, and
1107 then it will use your private key to decrypt it.</p>
1108
1109 <p>Notice the bar that Enigmail shows you above the message, with
1110 information about the status of Edward's key.</p>
1111
1112 </div><!-- End .main -->
1113 </div><!-- End #step-3e .step -->
1114 </div></section>
1115
1116 <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
1117 <section class="row" id="section4"><div>
1118
1119 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
1120 <div class="section-intro">
1121
1122 <h2><em>#4</em> Learn the Web of Trust</h2>
1123
1124 <p>Email encryption is a powerful technology, but it has a weakness;
1125 it requires a way to verify that a person's public key is actually
1126 theirs. Otherwise, there would be no way to stop an attacker from making
1127 an email address with your friend's name, creating keys to go with it and
1128 impersonating your friend. That's why the free software programmers that
1129 developed email encryption created keysigning and the Web of Trust.</p>
1130
1131 <p>When you sign someone's key, you are publicly saying that you've verified
1132 that it belongs to them and not someone else.</p>
1133
1134 <p>Signing keys and signing messages use the same type of mathematical
1135 operation, but they carry very different implications. It's a good practice
1136 to generally sign your email, but if you casually sign people's keys, you
1137 may accidently end up vouching for the identity of an imposter.</p>
1138
1139 <p>People who use your public key can see who has signed it. Once you've
1140 used GnuPG for a long time, your key may have hundreds of signatures. You
1141 can consider a key to be more trustworthy if it has many signatures from
1142 people that you trust. The Web of Trust is a constellation of GnuPG users,
1143 connected to each other by chains of trust expressed through signatures.</p>
1144
1145 </div><!-- End .section-intro -->
1146
1147 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1148 <div id="step-4a" class="step">
1149 <div class="sidebar">
1150
1151 <p><img
1152 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png"
1153 alt="Section 4: Web of Trust" /></p>
1154
1155 </div><!-- /.sidebar -->
1156 <div class="main">
1157
1158 <h3><em>Step 4.a</em> Sign a key</h3>
1159
1160 <p>In your email program's menu, go to Enigmail &rarr; Key Management.</p>
1161
1162 <p>Right click on Edward's public key and select Sign Key from the context
1163 menu.</p>
1164
1165 <p>In the window that pops up, select "I will not answer" and click ok.</p>
1166
1167 <p>Now you should be back at the Key Management menu. Select Keyserver &rarr;
1168 Upload Public Keys and hit ok.</p>
1169
1170 <p class="notes">You've just effectively said "I trust that Edward's public
1171 key actually belongs to Edward." This doesn't mean much because Edward isn't
1172 a real person, but it's good practice.</p>
1173
1174 <!--<div id="pgp-pathfinder">
1175
1176 <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi"
1177 method="get">
1178
1179 <p><strong>From:</strong><input type="text" value="xD41A008"
1180 name="FROM"></p>
1181
1182 <p><strong>To:</strong><input type="text" value="50BD01x4" name="TO"></p>
1183
1184 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"><input
1185 type="reset" value="reset" name=".reset"></p>
1186
1187 </form>
1188
1189 </div>End #pgp-pathfinder -->
1190 </div><!-- End .main -->
1191 </div><!-- End #step-4a .step -->
1192
1193 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1194 <div id="step-identify_keys" class="step">
1195 <div class="main">
1196
1197 <h3>Identifying keys: Fingerprints and IDs</h3>
1198
1199 <p>People's public keys are usually identified by their key fingerprint,
1200 which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8
1201 (for Edward's key). You can see the fingerprint for your public key, and
1202 other public keys saved on your computer, by going to Enigmail &rarr; Key
1203 Management in your email program's menu, then right clicking on the key
1204 and choosing Key Properties. It's good practice to share your fingerprint
1205 wherever you share your email address, so that people can double-check that
1206 they have the correct public key when they download yours from a keyserver.</p>
1207
1208 <p class="notes">You may also see public keys referred to by a shorter
1209 key ID. This key ID is visible directly from the Key Management
1210 window. These eight character key IDs were previously used for
1211 identification, which used to be safe, but is no longer reliable. You
1212 need to check the full fingerprint as part of verifying you have the
1213 correct key for the person you are trying to contact. Spoofing, in
1214 which someone intentionally generates a key with a fingerprint whose
1215 final eight characters are the same as another, is unfortunately
1216 common.</p>
1217
1218 </div><!-- End .main -->
1219 </div><!-- End #step-identify_keys .step-->
1220
1221 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1222 <div id="check-ids-before-signing" class="step">
1223 <div class="main">
1224
1225 <h3><em>Important:</em> What to consider when signing keys</h3>
1226
1227 <p>Before signing a person's key, you need to be confident that it actually
1228 belongs to them, and that they are who they say they are. Ideally, this
1229 confidence comes from having interactions and conversations with them over
1230 time, and witnessing interactions between them and others. Whenever signing
1231 a key, ask to see the full public key fingerprint, and not just the shorter
1232 key ID. If you feel it's important to sign the key of someone you've just
1233 met, also ask them to show you their government identification, and make
1234 sure the name on the ID matches the name on the public key. In Enigmail,
1235 answer honestly in the window that pops up and asks "How carefully have you
1236 verified that the key you are about to sign actually belongs to the person(s)
1237 named above?"</p>
1238
1239 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
1240 <div class="troubleshooting">
1241
1242 <h4>Advanced</h4>
1243
1244 <dl>
1245 <dt>Master the Web of Trust</dt>
1246 <dd>Unfortunately, trust does not spread between users the way <a
1247 href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people
1248 think</a>. One of best ways to strengthen the GnuPG community is to deeply <a
1249 href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of
1250 Trust and to carefully sign as many people's keys as circumstances permit.</dd>
1251
1252 <dt>Set ownertrust</dt>
1253 <dd>If you trust someone enough to validate other people's keys, you can assign
1254 them an ownertrust level through Enigmails's key management window. Right
1255 click on the other person's key, go to the "Select Owner Trust" menu option,
1256 select the trustlevel and click OK. Only do this once you feel you have a
1257 deep understanding of the Web of Trust.</dd>
1258 </dl>
1259
1260 </div><!-- /.troubleshooting -->
1261 </div><!-- End .main -->
1262 </div><!-- End #check-ids-before-signing .step-->
1263 </div></section><!-- End #section4 -->
1264
1265 <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
1266 <section id="section5" class="row"><div>
1267
1268 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
1269 <div class="section-intro">
1270
1271 <h2><em>#5</em> Use it well</h2>
1272
1273 <p>Everyone uses GnuPG a little differently, but it's important to follow
1274 some basic practices to keep your email secure. Not following them, you
1275 risk the privacy of the people you communicate with, as well as your own,
1276 and damage the Web of Trust.</p>
1277
1278 </div><!-- End .section-intro -->
1279
1280 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1281 <div id="step-5a" class="step">
1282 <div class="sidebar">
1283
1284 <p><img
1285 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png"
1286 alt="Section 5: Use it Well (1)" /></p>
1287
1288 </div><!-- /.sidebar -->
1289 <div class="main">
1290
1291 <h3>When should I encrypt? When should I sign?</h3>
1292
1293 <p>The more you can encrypt your messages, the better. If you only encrypt
1294 emails occasionally, each encrypted message could raise a red flag for
1295 surveillance systems. If all or most of your email is encrypted, people
1296 doing surveillance won't know where to start. That's not to say that only
1297 encrypting some of your email isn't helpful -- it's a great start and it
1298 makes bulk surveillance more difficult.</p>
1299
1300 <p>Unless you don't want to reveal your own identity (which requires other
1301 protective measures), there's no reason not to sign every message, whether or
1302 not you are encrypting. In addition to allowing those with GnuPG to verify
1303 that the message came from you, signing is a non-intrusive way to remind
1304 everyone that you use GnuPG and show support for secure communication. If you
1305 often send signed messages to people that aren't familiar with GnuPG, it's
1306 nice to also include a link to this guide in your standard email signature
1307 (the text kind, not the cryptographic kind).</p>
1308
1309 </div><!-- End .main -->
1310 </div><!-- End #step-5a .step -->
1311
1312 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1313 <div id="step-5b" class="step">
1314 <div class="sidebar">
1315
1316 <p><img
1317 src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png"
1318 alt="Section 5: Use it Well (2)" /></p>
1319
1320 </div><!-- /.sidebar -->
1321 <div class="main">
1322
1323 <h3>Be wary of invalid keys</h3>
1324
1325 <p>GnuPG makes email safer, but it's still important to watch out for invalid
1326 keys, which might have fallen into the wrong hands. Email encrypted with
1327 invalid keys might be readable by surveillance programs.</p>
1328
1329 <p>In your email program, go back to the first encrypted email that Edward
1330 sent you. Because Edward encrypted it with your public key, it will have a
1331 message from Enigmail at the top, which most likely says "Enigmail: Part of
1332 this message encrypted."</p>
1333
1334 <p><b>When using GnuPG, make a habit of glancing at that bar. The program
1335 will warn you there if you get an email signed with a key that can't
1336 be trusted.</b></p>
1337
1338 </div><!-- End .main -->
1339 </div><!-- End #step-5b .step -->
1340
1341 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1342 <div id="step-5c" class="step">
1343 <div class="main">
1344
1345 <h3>Copy your revocation certificate to somewhere safe</h3>
1346
1347 <p>Remember when you created your keys and saved the revocation certificate
1348 that GnuPG made? It's time to copy that certificate onto the safest digital
1349 storage that you have -- the ideal thing is a flash drive, disk, or hard
1350 drive stored in a safe place in your home, not on a device you carry with
1351 you regularly.</p>
1352
1353 <p>If your private key ever gets lost or stolen, you'll need this certificate
1354 file to let people know that you are no longer using that keypair.</p>
1355
1356 </div><!-- End .main -->
1357 </div><!-- End #step-5c .step -->
1358
1359 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1360 <div id="step-lost_key" class="step">
1361 <div class="main">
1362
1363 <h3><em>Important:</em> act swiftly if someone gets your private key</h3>
1364
1365 <p>If you lose your private key or someone else gets ahold
1366 of it (say, by stealing or cracking your computer), it's
1367 important to revoke it immediately before someone else uses
1368 it to read your encrypted email or forge your signature. This
1369 guide doesn't cover how to revoke a key, but you can follow these <a
1370 href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>.
1371 After you're done revoking, make a new key and send an email to everyone
1372 with whom you usually use your key to make sure they know, including a copy
1373 of your new key.</p>
1374
1375 </div><!-- End .main -->
1376 </div><!-- End #step-lost_key .step-->
1377
1378 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1379 <!---<div id="transfer-key" class="step">
1380 <div class="main">
1381
1382 <h3>Transferring you key</h3>
1383
1384 <p>You can use Enigmail's <a
1385 href="https://www.enigmail.net/documentation/Key_Management">key management
1386 window</a> to import and export keys. If you want to be able to read
1387 your encrypted email on a different computer, you will need to export
1388 your secret key from here. Be warned, if you transfer the key without <a
1389 href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a>
1390 the drive it's on the transfer will be dramatically less secure.</p>
1391
1392 </div>--><!-- End .main
1393 </div> End #transfer-key .step-->
1394
1395 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
1396 <div id="webmail-and-GnuPG" class="step">
1397 <div class="main">
1398
1399 <h3>Webmail and GnuPG</h3>
1400
1401 <p>When you use a web browser to access your email, you're using webmail,
1402 an email program stored on a distant website. Unlike webmail, your desktop
1403 email program runs on your own computer. Although webmail can't decrypt
1404 encrypted email, it will still display it in its encrypted form. If you
1405 primarily use webmail, you'll know to open your email client when you receive
1406 a scrambled email.</p>
1407
1408 </div><!-- End .main -->
1409 </div><!-- End #webmail-and-GnuPG .step-->
1410
1411 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
1412 <div id="step-5d" class="step">
1413 <div class="main">
1414
1415 <h3>Make your public key part of your online identity</h3>
1416
1417 <p> First add your public key fingerprint to your email signature, then
1418 compose an email to at least five of your friends, telling them you just
1419 set up GnuPG and mentioning your public key fingerprint. Link to this guide
1420 and ask them to join you. Don't forget that there's also an awesome <a
1421 href="infographic.html">infographic to share.</a></p>
1422
1423 <p class="notes">Start writing your public key fingerprint anywhere someone
1424 would see your email address: your social media profiles, blog, Website,
1425 or business card. (At the Free Software Foundation, we put ours on our
1426 <a href="https://fsf.org/about/staff">staff page</a>.) We need to get our
1427 culture to the point that we feel like something is missing when we see an
1428 email address without a public key fingerprint.</p>
1429
1430 </div>--><!-- End .main
1431 </div> End #step-5d .step-->
1432 </div></section><!-- End #section5 -->
1433
1434 <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
1435 <section class="row" id="section6">
1436 <div id="step-click_here" class="step">
1437 <div class="main">
1438
1439 <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>
1440
1441 </div><!-- End .main -->
1442 </div><!-- End #step-click_here .step-->
1443 </section><!-- End #section6 -->
1444
1445 <!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
1446 <!-- When un-commenting this section go to main.css and search
1447 for /* Guide Sections Background */ then add #faq to the desired color
1448 <section class="row" id="faq"><div>
1449 <div class="sidebar">
1450
1451 <h2>FAQ</h2>
1452
1453 </div>
1454 <div class="main">
1455
1456 <dl>
1457 <dt>My key expired</dt>
1458 <dd>Answer coming soon.</dd>
1459
1460 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
1461 <dd>Answer coming soon.</dd>
1462
1463 <dt>My email program is opening at times I don't want it to open/is now my
1464 default program and I don't want it to be.</dt>
1465 <dd>Answer coming soon.</dd>
1466 </dl>
1467
1468 </div>
1469 </div>
1470 </section> --><!-- End #faq -->
1471
1472 <!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
1473 <footer class="row" id="footer"><div>
1474 <div id="copyright">
1475
1476 <h4><a href="https://u.fsf.org/ys"><img
1477 alt="Free Software Foundation"
1478 src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" /></a></h4>
1479
1480 <p>Copyright &copy; 2014-2016 <a
1481 href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a
1482 href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please
1483 support our work by <a href="https://u.fsf.org/yr">joining us as an associate
1484 member.</a></p>
1485
1486 <p>The images on this page are under a <a
1487 href="https://creativecommons.org/licenses/by/4.0/">Creative Commons
1488 Attribution 4.0 license (or later version)</a>, and the rest of it is under
1489 a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons
1490 Attribution-ShareAlike 4.0 license (or later version)</a>. Download the <a
1491 href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
1492 source code of Edward reply bot</a> by Andrew Engelbrecht
1493 &lt;andrew@engelbrecht.io&gt; and Josh Drake &lt;zamnedix@gnu.org&gt;,
1494 available under the GNU Affero General Public License. <a
1495 href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these
1496 licenses?</a></p>
1497
1498 <p>Fonts used in the guide &amp; infographic: <a
1499 href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo
1500 Impallari, <a href="http://www.google.com/fonts/specimen/Signika">Signika</a>
1501 by Anna Giedry&#347;, <a
1502 href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo
1503 Narrow</a> by Omnibus-Type, <a
1504 href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a>
1505 by Florian Cramer.</p>
1506
1507 <p>Download the <a href="emailselfdefense_source.zip">source package</a>
1508 for this guide, including fonts, image source files and the text of Edward's
1509 messages.</p>
1510
1511 <p>This site uses the Weblabels standard for labeling <a
1512 href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View
1513 the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
1514 rel="jslicense">source code and license information</a>.</p>
1515
1516 </div><!-- /#copyright -->
1517
1518 <p class="credits">Infographic and guide design by <a rel="external"
1519 href="http://jplusplus.org"><strong>Journalism++</strong><img
1520 src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png"
1521 alt="Journalism++" /></a></p><!-- /.credits -->
1522 </div></footer><!-- End #footer -->
1523
1524
1525 <script type="text/javascript"
1526 src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
1527 <script type="text/javascript"
1528 src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
1529 <!-- Piwik -->
1530 <script type="text/javascript">
1531   // @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&dn=gpl-2.0.txt GPL-2.0-or-later
1532   var _paq = _paq || [];
1533   _paq.push(["trackPageView"]);
1534   _paq.push(["enableLinkTracking"]);
1535
1536   (function() {
1537     var u = (("https:" == document.location.protocol) ? "https" : "http") + "://"+"piwik.fsf.org//";
1538     _paq.push(["setTrackerUrl", u+"piwik.php"]);
1539     _paq.push(["setSiteId", "13"]);
1540     var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
1541     g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
1542   })();
1543   // @license-end
1544 </script>
1545 <!-- End Piwik Code -->
1546 <!-- Piwik Image Tracker -->
1547 <noscript><img src="https://piwik.fsf.org//piwik.php?idsite=13&rec=1" style="border:0" alt="" /></noscript>
1548 <!-- End Piwik -->
1549 </body>
1550 </html>