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