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