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