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