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