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