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