sv/index.html

   1 <!DOCTYPE html>
   2 <html>
   3 <head>
   4         <meta http-equiv="content-type" content="text/html; charset=utf-8" />
   5
   6         <title>Mejl Självförsvar - en vägledning för att bekämpa övervakning med GnuPG kryptering</title>
   7         <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, övervakning, integritet, privacy, email, mejl, Enigmail" />
   8         <meta name="description" content="Övervakning av mejl bryter mot våra fundamentala rättigheter och gör yttrandefrihet riskabel. Den här guiden lär dig självförsvar för mejl på 30 minuter med GnuPG." />
   9
  10         <meta name="viewport" content="width=device-width, initial-scale=1" />
  11         <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />
  12         <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
  13
  14 </head>
  15 <body>
  16
  17         <!-- ~~~~~~~~~ GnuPG Header and introduction text  ~~~~~~~~~ -->
  18
  19         <header class="row"  id="header">
  20                 <div>
  21                         <h1>Mejl Självförsvar</h1>
  22
  23                         <!-- Language list for browsers that do not have JS enabled -->
  24                         <ul id="languages" class="os">
  25                 <li><a class="current" href="/se">svenska</a></li>
  26                 <li><a href="/en">english</a></li>
  27                                 <li><a href="/es">español - v3.0</a></li>
  28                                 <li><a href="/fr">français - v3.0</a></li>
  29                                 <li><a href="/de">deutsch - v3.0</a></li>
  30                                 <li><a href="/it">italiano - v3.0</a></li>
  31                                 <li><a href="/pt-br">português do Brasil - v3.0</a></li>
  32                                 <li><a href="/tr">türkçe - v3.0</a></li>
  33                                 <li><a href="/ro">română - v3.0</a></li>
  34                                 <li><a href="/ru">русский - v3.0</a></li>
  35                                 <!--<li><a href="/ml">മലയാളം</a></li>-->
  36                                 <!--<li><a href="/ko">한국어</a></li>-->
  37                                 <li><a href="/ja">日本語 - v3.0</a></li>
  38                                 <li><a href="/el">ελληνικά - v3.0</a></li>
  39                                 <!--<li><a href="/ar">العربية</a></li>-->
  40                                 <li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span style="color: #2F5FAA;">Translate!</span></strong></a></li>
  41                         </ul>
  42
  43                         <ul id="menu" class="os">
  44                                 <li class="spacer">
  45                                         <a href="index.html" class="current">GNU/Linux</a>
  46                                 </li>
  47                                 <li>
  48                                         <a href="mac.html">Mac OS</a>
  49                                 </li>
  50                                 <li>
  51                                         <a href="windows.html">Windows</a>
  52                                 </li>
  53                                 <li class="spacer"><a href="workshops.html">Teach your friends</a></li>
  54                                 <li class="spacer">
  55                                         <a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Självförsvar för mejl för alla via %40fsf">
  56                                                 Share&nbsp;
  57                                                 <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
  58                                                 class="share-logo" alt="[GNU Social]">&nbsp;
  59                                                 <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
  60                                                 class="share-logo" alt="[Pump.io]">&nbsp;
  61                                                 <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"
  62                                                 class="share-logo" alt="[Reddit]">&nbsp;
  63                                                 <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"
  64                                                 class="share-logo" alt="[Hacker News]">
  65                                         </a>
  66                                 </li>
  67                         </ul>
  68
  69                         <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
  70                         <div id="fsf-intro">
  71                                 <h3>
  72                                         <a href="http://u.fsf.org/ys">
  73                                                 <img alt="Free Software Foundation"
  74                                                 src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
  75                                         </a>
  76                                 </h3>
  77                                 <div class="fsf-emphasis">
  78                                         <p>
  79                                                 Vi kämpar för datoranvändares rättigheter, och främjar utvecklingen av fri (som i frihet) programvara. Att motarbeta mass-övervakning är mycket viktigt för oss.
  80                                         </p>
  81                                         <p>
  82                                                 <strong>
  83                             Vänligen bidra för att stödja Mejl Självförsvar. Vi behöver fortsätta förbättra guiden och annat liknande material, till förmån för människor i hela världen som tar första stegen mot att försvara sin integritet.
  84                                                 </strong>
  85                                         </p>
  86                                 </div>
  87
  88                                 <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&amp;id=14&amp;pk_campaign=email_self_defense&amp;pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png"   /></a>  </p>
  89
  90                         </div><!-- End #fsf-intro -->
  91
  92                         <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
  93                         <div class="intro">
  94                                 <p>
  95                                         <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" alt="View &amp; share our infographic &rarr;" /></a>Övervakning av mejl bryter mot våra fundamentala rättigheter och gör yttrandefrihet riskabel. Den här guiden lär dig ett grundläggande självförsvar mot övervakning: kryptering av mejl. När du är klar, kommer du att kunna skicka och ta emot mejl som är förvrängda för att säkerställa att en övervakningsagent eller tjuv som kommit över ditt mejl inte kan läsa det. Allt du behöver är en dator med internet-uppkoppling, ett mejl-konto och ungefär fyrtio minuter.</p>
  96
  97                                         <p>Även om du inte har något att dölja, så skyddar kryptering integriteten hos de som du kommunicerar med, och gör det krångligt för övervakningssystem. Om du har något att dölja så är du i gott sällskap; det här är samma verktyg som visselblåsare använder för att sätta ljus på missbruk mot mänskliga rättighter, korruption och andra brott.</p>
  98
  99 <p>Att stå upp i kampen mot övervaknig kräver, förutom att använda kryptering, politiskt engagemang för en <a href="http://gnu.org/philosophy/surveillance-vs-democracy.html"> begränsning av datat som sparas om oss</a>, men det väsentliga första steget är att försvara dig själv, att göra övervakning av din kommunikation så svår som möjligt. Den här guiden hjälper dig göra det. Den är anpassad för nybörjare, men om du redan kan grunderna i GnuPG, eller är en erfaren användare av fri mjukvara, så kommer du att ha nytta av de avancerade tipsen och vår <a href="workshops.html"> guide till att lära dina vänner.</a> </p>
 100
 101                                 </div><!-- End .intro -->
 102
 103                         </div>
 104                 </header><!-- End #header -->
 105
 106                 <!-- ~~~~~~~~~ Section 1: Get the pieces  ~~~~~~~~~ -->
 107                 <section class="row" id="section1">
 108                         <div>
 109                                 <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 110                                 <div class="section-intro">
 111                                         <h2><em>#1</em> Samla ihop verktygen</h2>
 112                                         <p class="notes">Den här guiden förlitar sig på programvara som kommer med <a href="https://www.gnu.org/philosophy/free-sw.en.html">fria licenser</a>; programvara som är helt transparenta, vem som helst kan kopiera eller göra sin egen version av den. Det gör den säkrare från övervakningssynpunkt än proprietära program (som Windows). Lär mer om fri programvara på <a href="https://u.fsf.org/ys">fsf.org</a>.</p>
 113
 114 <p>De flesta distributionerna av GNU/Linux operativsystem kommer med GnuPG förinstallerat, så det behöver du inte ladda ned. Men innan du konfigurerar GnuPG så behöver du mejlprogrammet IceDove installerat på din dator. GNU/Linux-distributioner har vanligtvis IceDove tillgängligt för installation, men det kanske hittas under namnet "Thunderbird". Mejlprogram är ett annat sätt att komma åt samma mejlkonton som du kan komma åt via en webbläsare (som Gmail), men erbjuder ytterligare funktioner. </p>
 115
 116                                         <p>Om du redan har ett mejlprogram, så kan du skippa till <a href="#step-1b">Steg 1.b</a>.</p>
 117
 118                                 </div><!-- End .section-intro -->
 119
 120                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 121                                 <div id="step-1a" class="step">
 122                                         <div class="sidebar">
 123                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
 124                                         </div><!-- /.sidebar -->
 125                                         <div class="main">
 126                                                 <h3><em>Steg 1.a</em> Ställ in ditt mejlprogram för ditt mejlkonto</h3>
 127                                                 <p>Öppna ditt mejlprogram och följ instruktionerna (steg-för-steg genomgång) som ställer in programmet för ditt mejlkonto</p>
 128
 129 <p>Titta efter bokstäverna SSL, TLS eller STARTTLS till höger om servrarna när du ställer in ditt konto. Om du inte ser dem, kan du ändå sätta upp ditt konto. Men, det betyder att de som sköter om ditt mejl-system inte har följt med i industristandarden när det gäller att skydda din säkerhet och integritet. Vi rekommenderar att du skickar ett vänligt mejl och ber dem att aktivera SSL, TLS eller STARTTLS för din mejl-server. De kommer att veta vad du pratar om, så det är värt en begäran, även om du inte är en expert på dessa säkerhetsteknologier.</p>
 130
 131                                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 132                                                 <div class="troubleshooting">
 133                                                         <h4>Problemlösning</h4>
 134                                                         <dl>
 135                                                                 <dt>Assistenten startar inte</dt>
 136                                                                 <dd>Du kan starta assisten själv, men menyvalet för att göra det ser annorlunda ut i olika mejlprogram. Knappen för att starta assistenten kommer att vara under programmets huvudmeny, under "Ny" eller liknande, benämd "Lägg till konto", eller, "Nytt/Befintligt mejlkonto."</dd>
 137                                                                 <dt>Assistenten kan inte hitta mitt konto eller laddar inte ned mina mejl</dt>
 138                                                                 <dd>Innan du söker på nätet, rekommenderar vi att du börjar med att fråga andra personer som använder samma mejlsystem, för att klura ut korrekt inställningar</dd>
 139                                                                 <dt class="feedback">Ser ingen lösning på ditt problem?</dt>
 140                                                                 <dd class="feedback">Vänligen låt oss veta på <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
 141                                                         </dl>
 142                                                 </div><!-- /.troubleshooting -->
 143
 144                                         </div><!-- End .main -->
 145                                 </div><!-- End #step1-a .step -->
 146
 147                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 148                                 <div id="step-1b" class="step">
 149                                         <div class="sidebar">
 150                                                 <ul class="images">
 151                                                         <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
 152                                                         <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png" alt="Step 1.B: Search Add-ons" /></li>
 153                                                         <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png" alt="Step 1.B: Install Add-ons" /></li>
 154                                                 </ul>
 155                                         </div><!-- /.sidebar -->
 156                                         <div class="main">
 157                                                 <h3><em>Steg 1.b</em> Installera Enigmail-pluginen för ditt mejlprogram</h3>
 158                                                 <p>I ditt mejlprograms meny, välj Add-ons (det kan ligga under sektionen Verktyg). Säkerställ att Tillägg är valt till vänster. Ser du Enigmail? I så fall, skippa det här steget.</p>
 159                                                 <p>Om inte, sök efter "Enigmail" i sökfältet uppe till höger. Du klarar det härifrån. Starta om ditt mejlprogram när du är klar.</p>
 160                                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 161                                                 <div class="troubleshooting">
 162                                                         <h4>Problemlösning</h4>
 163                                                         <dl>
 164
 165                                                                 <dt>Jag kan inte hitta menyn.</dt>
 166                                                                 <dd>I många nya mejlprogram är huvudmenyn representerad av en bild på tre horisontella streck.</dd>
 167                                                                 <dt>Mina mejl ser konstiga ut</dt>
 168
 169                                                                 <dd>Enigmail tenderar att inte fungera så väl med HTML som används för att formatera mejl, så Enigmail har kanske inaktiverat HTML-formatering automatiskt. För att skicka ett mejl i HTML-format utan kryptering eller signatur, håll ned Skift-tangenten när du trycker på "Nytt" eller "Compose". Då kan du skriva ett mejl som om Enigmail inte var där.</dd>
 170
 171                                                                 <dt class="feedback">Ser ingen lösning på ditt problem?</dt>
 172                                                                 <dd class="feedback">Vänligen låt oss veta på <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback-sidan</a>.</dd>
 173                                                         </dl>
 174                                                 </div><!-- /.troubleshooting -->
 175                                         </div><!-- End .main -->
 176                                 </div><!-- End #step-1b .step -->
 177
 178                         </div>
 179                 </section><!-- End #section1 -->
 180
 181                 <!-- ~~~~~~~~~ Section 2: Make your keys  ~~~~~~~~~ -->
 182                 <section class="row" id="section2">
 183                         <div>
 184                                 <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 185                                 <div class="section-intro">
 186                                         <h2><em>#2</em> Ta fram dina nycklar</h2>
 187                                         <p>För att använda systemet GnuPG, behöver du en publik och en privat nyckel, (tillsammans bildar de ett nyckelpar). Varje nyckel är en lång sträng av slumpvis genererade siffror och bokstäver som är unika för dig. Din publika och privata nyckel är hop-länkade med en speciell matematisk funktion.</p>
 188
 189                                         <p>Din publika nyckel är inte som en fysisk nyckel, den är förvarad i det öppna i ett uppkopplat arkiv som kallas nyckelserver (keyserver). Andra laddar ned den och använder den tillsammans med GnuPG, för att kryptera meddelanden som de skickar till dig. Du kan tänka på nyckelservern som en telefonbok; andra som vill skicka ett krypterat meddelande till dig kan leta upp din publika nyckel.</p>
 190
 191                                         <p>Din privata nyckel är mer som en fysisk nyckel, för du behåller den för dig själv (på din dator). Du använder GnuPG och din privata nyckel ihop för att dekryptera krypterade mejl som andra har skickat till dig.  <span style="font-weight: bold;">Du bör aldrig, under några omständigheter, dela din privata nyckel med någon.</span></p>
 192
 193                                         <p>Förutom kryptering och dekryptering, kan du använda dessa nycklar för att signera meddelanden och kontrollera äktheten hos andras signaturer. Vi ska diskutera mer om det in nästa steg. </p>
 194                                 </div><!-- End .section-intro -->
 195
 196                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 197                                 <div id="step-2a" class="step">
 198                                         <div class="sidebar">
 199                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
 200                                         </div><!-- /.sidebar -->
 201                                         <div class="main">
 202                                                 <h3><em>Steg 2.a</em> Gör ett nyckelpar</h3>
 203
 204                                                 <p>Enigmail-Assistenten startar kanske upp automatiskt. Om den inte gör det, välj Enigmail &rarr; Enigmail-Assistenten från ditt mejlprograms meny. Du behöver inte läsa texten som poppar upp om du inte vill, men det är bra att läsa texten på de senare sidorna av assistenten. Klicka på nästa med de förinställda optionerna valda, förutom de som är listade här i den ordning de dyker upp:</p>
 205
 206                                                 <ul>
 207                                                         <li>På sidan med titeln "Kryptering", välj "Kryptera alla mina meddelanden som förval, för integritet är kritiskt för mig."</li>
 208
 209                                                         <li>On the screen titled "Signing," select "Don't sign my messages by default."</li>
 210                                                         <li>On the screen titled "Key Selection," select "I want to create a new key pair for signing and encrypting my email."</li>
 211                                                         <li>On the screen titled "Create Key," pick a strong password! You can do it manually, or you can use the Diceware method. Doing it manually is faster but not as secure. Using Diceware takes longer and requires dice, but creates a password that is much harder for attackers figure out. To use it, read the section "Make a secure passphrase with Diceware" in <a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">this article</a> by Micah Lee.</p>
 212 </a>
 213                                                         </ul>
 214
 215                                                         <p>If you'd like to pick a password manually, come up with something you can remember which is at least twelve characters long, and includes at least one lower case and upper case letter and at least one number or punctuation symbol. Never pick a password you've used elsewhere. Don't use any recognizable patterns, such as birthdays, telephone numbers, pets' names, song lyrics, quotes from books, and so on.</p>
 216
 217                                                         <p class="notes">The program will take a little while to finish the next step, the "Key Creation" screen. While you wait, do something else with your computer, like watching a movie or browsing the Web. The more you use the computer at this point, the faster the key creation will go.</p>
 218                                                         <p><span style="font-weight: bold;">When the "Key Generation Completed" screen pops up, select Generate Certificate and choose to save it in a safe place on your computer (we recommend making a folder called "Revocation Certificate" in your home folder and keeping it there). This step is essential for your email self-defense, as you'll learn more about in <a href="#section5">Section 5</a>.</span></p>
 219
 220
 221                                                         <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 222                                                         <div class="troubleshooting">
 223                                                                 <h4>Troubleshooting</h4>
 224                                                                 <dl>
 225                                                                         <dt>I can't find the Enigmail menu.</dt>
 226                                                                         <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars. Enigmail may be inside a section called Tools.</dd>
 227
 228                                                                         <dt>The wizard says that it cannot find GnuPG.</dt>
 229                                                                         <dd>Open whatever program you usually use for installing software, and search for GnuPG, then install it. Then restart the  Enigmail setup wizard by going to Enigmail &rarr; Setup Wizard.</dd>
 230
 231                                                                         <dt>My email looks weird</dt>
 232                                                                         <dd>Enigmail doesn't tend to play nice with HTML, which is used to format emails, so it may disable your HTML formatting automatically. To send an HTML-formatted email without encryption or a signature, hold down the Shift key when you select compose. You can then write an email as if Enigmail wasn't there.</dd>
 233
 234                                                                         <dt>More resources</dt>
 235                                                                         <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">Enigmail's wiki instructions for key generation</a>.</dd>
 236
 237
 238
 239                                                                         <dt class="feedback">Don't see a solution to your problem?</dt>
 240                                                                         <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
 241                                                                 </dl>
 242                                                         </div><!-- /.troubleshooting -->
 243                                                         <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 244
 245                                                         <div class="troubleshooting">
 246                                                                 <h4>Advanced</h4>
 247                                                                 <dl>
 248
 249
 250                                                                         <dt>Command line key generation</dt>
 251                                                                         <dd>If you prefer using the command line for a higher degree of control, you can follow the documentation from <a href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy Handbook</a>. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than the algorithms the documentation recommends. Also make sure your key is at least 2048 bits, or 4096 if you want to be extra secure.</dd>
 252
 253                                                                         <dt>Advanced key pairs</dt>
 254                                                                         <dd>When GnuPG creates a new keypair, it compartmentalizes the encryption function from the signing function through <a href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use subkeys carefully, you can keep your GnuPG identity much more secure and recover from a compromised key much more quickly. <a href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a> and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a> provide good guides for setting up a secure subkey configuration.</dd>
 255                                                                 </dl>
 256                                                         </div><!-- /.troubleshooting -->
 257                                                 </div><!-- End .main -->
 258                                         </div><!-- End #step-2a .step  -->
 259
 260
 261
 262                                         <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 263                                         <div id="step-2b" class="step">
 264                                                 <div class="main">
 265                                                         <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
 266                                                         <p>In your email program's menu, select Enigmail &rarr; Key Management.</p>
 267                                                         <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
 268                                                         <p class="notes">Now someone who wants to send you an encrypted message can download your public key from the Internet. There are multiple keyservers that you can select from the menu when you upload, but they are all copies of each other, so it doesn't matter which one you use. However, it sometimes takes a few hours for them to match each other when a new key is uploaded.</p>
 269                                                         <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 270                                                         <div class="troubleshooting">
 271                                                                 <h4>Troubleshooting</h4>
 272                                                                 <dl>
 273                                                                         <dt>The progress bar never finishes</dt>
 274                                                                         <dd>Close the upload popup, make sure you are connected to the Internet, and try again. If that doesn't work, try again, selecting a different keyserver.</dd>
 275                                                                         <dt>My key doesnt appear in the list</dt>
 276                                                                         <dd>Try checking "Display All Keys by Default."</dd>
 277                                                                         <dt>More documentation</dt>
 278                                                                         <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">Enigmail's documentation</a>.</dd>
 279
 280                                                                         <dt class="feedback">Don't see a solution to your problem?</dt>
 281                                                                         <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
 282
 283                                                                 </dl>
 284                                                         </div><!-- /.troubleshooting -->
 285
 286                                                         <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 287                                                         <div class="troubleshooting">
 288                                                                 <h4>Advanced</h4>
 289                                                                 <dl>
 290                                                                         <dt>Uploading a key from the command line</dt>
 291                                                                         <dd>You can also upload your keys to a keyserver through the <a href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a> maintains a list of highly interconnected keyservers. You can also <a href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export your key</a> as a file on your computer.</dd>
 292
 293                                                                 </dl>
 294                                                         </div><!-- /.troubleshooting -->
 295                                                 </div><!-- End .main -->
 296                                         </div><!-- End #step-2b .step  -->
 297
 298                                         <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 299                                         <div id="terminology" class="step">
 300                                                 <div class="main">
 301                                                         <h3>GnuPG, OpenPGP, what?</h3>
 302                                                         <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG) is the program that implements the standard. Enigmail is a plug-in program for your email program that provides an interface for GnuPG.</p>
 303                                                 </div><!-- End .main -->
 304                                         </div><!-- End #terminology.step-->
 305
 306
 307                                 </div>
 308                         </section><!-- End #section2 -->
 309
 310                         <!-- ~~~~~~~~~ Section 3: Try it out  ~~~~~~~~~ -->
 311                         <section class="row" id="section3">
 312                                 <div>
 313                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 314                                         <div class="section-intro">
 315                                                 <h2><em>#3</em> Try it out!</h2>
 316                                                 <p>Now you'll try a test correspondence with a computer program named Edward, who knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>
 317
 318                                                 <!-- <p>NOTE: Edward is currently having some technical difficulties, so he may take a long time to respond, or not respond at all. We're sorry about this and we're working hard to fix it. Your key will still work even without testing with Edward.</p> -->
 319                                         </div><!-- End .section-intro -->
 320
 321                                         <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 322                                         <div id="step-3a" class="step">
 323                                                 <div class="sidebar">
 324                                                         <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
 325                                                 </div><!-- /.sidebar -->
 326                                                 <div class="main">
 327                                                         <h3><em>Step 3.a</em> Send Edward your public key</h3>
 328                                                         <p>This is a special step that you won't have to do when corresponding with real people. In your email program's menu, go to Enigmail &rarr; Key Management. You should see your key in the list that pops up. Right click on your key and select Send Public Keys by Email. This will create a new draft message, as if you had just hit the Write button.</p>
 329
 330                                                         <p>Address the message to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word (whatever you want) in the subject and body of the email. Don't send yet.</p>
 331
 332                                                         <p>The lock icon in the top left should be yellow, meaning encryption is
 333                                                                 turned on. We want this first special message to be unencrypted, so
 334                                                                 click the icon once to turn it off. The lock should become grey, with a
 335                                                                 blue dot on it (to alert you that the setting has been changed from the
 336                                                                 default). Once encryption is off, hit Send.</p>
 337
 338                                                                 <p class="notes">It may take two or three minutes for Edward to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide. Once he's responded, head to the next step. From here on, you'll be doing just the same thing as when corresponding with a real person.</p>
 339
 340                                                                 <p>When you open Edward's reply, GnuPG may prompt you for your password before using your private key to decrypt it.</p>
 341                                                         </div><!-- End .main -->
 342                                                 </div><!-- End #step-3a .step -->
 343
 344                                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 345                                                 <div id="step-3b" class="step">
 346                                                         <div class="main">
 347                                                                 <h3><em>Step 3.b</em> Send a test encrypted email</h3>
 348                                                                 <p>Write a new email in your email program, addressed to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject "Encryption test" or something similar and write something in the body.</p>
 349                                                                 <p>The lock icon in the top left of the window should be yellow, meaning encryption is on. This will be your default from now on.</p>
 350                                                                 <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll get to this in a moment.</p>
 351                                                                 <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
 352
 353                                                                 <p>To encrypt an email to Edward, you need his public key, so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>
 354
 355                                                                 <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Check the box in front of Edward's key and click Send.</p>
 356
 357                                                                 <p class="notes">Since you encrypted this email with Edward's public key, Edward's private key is required to decrypt it. Edward is the only one with his private key, so no one except him can decrypt it.</p>
 358                                                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 359                                                                 <div class="troubleshooting">
 360                                                                         <h4>Troubleshooting</h4>
 361                                                                         <dl>
 362                                                                                 <dt>Enigmail can't find Edward's key</dt>
 363                                                                                 <dd>Close the pop-ups that have appeared since you clicked Send. Make sure you are connected to the Internet and try again. If that doesn't work, repeat the process, choosing a different keyserver when it asks you to pick one.</dd>
 364                                                                                 <dt>Unscrambled messages in the Sent folder</dt>
 365                                                                                 <dd>Even though you can't decrypt messages encrypted to someone else's key, your email program will automatically save a copy encrypted to your public key, which you'll be able to view from the Sent folder like a normal email. This is normal, and it doesn't mean that your email was not sent encrypted.</dd>
 366                                                                                 <dt>More resources</dt>
 367                                                                                 <dd>If you're still having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">Enigmail's wiki</a>.</dd>
 368                                                                                 <dt class="feedback">Don't see a solution to your problem?</dt>
 369                                                                                 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
 370                                                                         </dl>
 371                                                                 </div><!-- /.troubleshooting -->
 372
 373
 374                                                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 375                                                                 <div class="troubleshooting">
 376                                                                         <h4>Advanced</h4>
 377                                                                         <dl>
 378                                                                                 <dt>Encrypt messages from the command line</dt>
 379                                                                                 <dd>You can also encrypt and decrypt messages and files from the <a href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>, if that's your preference. The option --armor makes the encrypted output appear in the regular character set.</dd>
 380                                                                         </dl>
 381                                                                 </div><!-- /.troubleshooting -->
 382
 383
 384                                                         </div><!-- End .main -->
 385                                                 </div><!-- End #step-3b .step -->
 386
 387                                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 388                                                 <div id="step-headers_unencrypted" class="step">
 389                                                         <div class="main">
 390                                                                 <h3><em>Important:</em> Security tips</h3>
 391                                                                 <p>Even if you encrypt your email, the subject line is not encrypted, so don't put private information there. The sending and receiving addresses aren't encrypted either, so a surveillance system can still figure out who you're communicating with. Also, surveillance agents will know that you're using GnuPG, even if they can't figure out what you're saying. When you send attachments, Enigmail will give you the choice to encrypt them or not, independent of the actual email.</p>
 392                                                         </div><!-- End .main -->
 393                                                 </div><!-- End #step-headers_unencrypted .step-->
 394
 395
 396                                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 397                                                 <div id="step-3c" class="step">
 398                                                         <div class="main">
 399                                                                 <h3><em>Step 3.c</em> Receive a response</h3>
 400                                                                 <p>When Edward receives your email, he will use his private key to decrypt it, then use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to encrypt his reply to you.</p>
 401
 402                                                                 <p class="notes">It may take two or three minutes for Edward to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide.</p>
 403                                                                 <p>When you receive Edward's email and open it, Enigmail will automatically detect that it is encrypted with your public key, and then it will use your private key to decrypt it.</p>
 404                                                                 <p>Notice the bar that Enigmail shows you above the message, with information about the status of Edward's key.</p>
 405                                                         </div><!-- End .main -->
 406                                                 </div><!-- End #step-3c .step -->
 407
 408
 409                                                 <div id="step-3d" class="step">
 410                                                         <div class="main">
 411                                                                 <h3><em>Step 3.d</em> Send a test signed email</h3>
 412                                                                 <p>GnuPG includes a way for you to sign messages and files, verifying that they came from you and that they weren't tampered with along the way. These signatures are stronger than their pen-and-paper cousins -- they're impossible to forge, because they're impossible to create without your private key (another reason to keep your private key safe).</p>
 413
 414                                                                 <p>You can sign messages to anyone, so it's a great way to make people aware that you use GnuPG and that they can communicate with you securely. If they don't have GnuPG, they will be able to read your message and see your signature. If they do have GnuPG, they'll also be able to verify that your signature is authentic.</p>
 415
 416                                                                 <p>To sign an email to Edward, compose any message to him and click the pencil icon next to the lock icon so that it turns gold. If you sign a message, GnuPG may ask you for your password before it sends the message, because it needs to unlock your private key for signing.</p>
 417
 418                                                                 <p>With the lock and pencil icons, you can choose whether each message will be encrypted, signed, both, or neither.</p>
 419                                                         </div>
 420                                                 </div>
 421
 422                                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 423                                                 <div id="step-3e" class="step">
 424                                                         <div class="main">
 425                                                                 <h3><em>Step 3.e</em> Receive a response</h3>
 426                                                                 <p>When Edward receives your email, he will use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature is authentic and the message you sent has not been tampered with.</p>
 427
 428                                                                 <p class="notes">It may take two or three minutes for Edward to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide.</p>
 429
 430                                                                 <p>Edward's reply will arrive encrypted, because he prefers to use encryption whenever possible. If everything goes according to plan, it should say "Your signature was verified." If your test signed email was also encrypted, he will mention that first.</p>
 431                                                         </div><!-- End .main -->
 432                                                 </div><!-- End #step-3c .step -->
 433                                         </div>
 434                                 </section>
 435
 436
 437                                 <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust  ~~~~~~~~~ -->
 438                                 <section class="row" id="section4">
 439                                         <div>
 440                                                 <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 441                                                 <div class="section-intro">
 442                                                         <h2><em>#4</em> Learn the Web of Trust</h2>
 443                                                         <p>Email encryption is a powerful technology, but it has a weakness; it requires a way to verify that a person's public key is actually theirs. Otherwise, there would be no way to stop an attacker from making an email address with your friend's name, creating keys to go with it and impersonating your friend. That's why the free software programmers that developed email encryption created keysigning and the Web of Trust.</p>
 444
 445                                                         <p>When you sign someone's key, you are publicly saying that you've verified that it belongs to them and not someone else.</p>
 446
 447                                                         <p>Signing keys and signing messages use the same type of mathematical operation, but they carry very different implications. It's a good practice to generally sign your email, but if you casually sign people's keys, you may accidently end up vouching for the identity of an imposter.</p>
 448
 449                                                         <p>People who use your public key can see who has signed it. Once you've used GnuPG for a long time, your key may have hundreds of signatures. You can consider a key to be more trustworthy if it has many signatures from people that you trust. The Web of Trust is a constellation of GnuPG users, connected to each other by chains of trust expressed through signatures.</p>
 450
 451                                                 </div><!-- End .section-intro -->
 452
 453                                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 454                                                 <div id="step-4a" class="step">
 455                                                         <div class="sidebar">
 456                                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
 457                                                         </div><!-- /.sidebar -->
 458                                                         <div class="main">
 459                                                                 <h3><em>Step 4.a</em> Sign a key</h3>
 460                                                                 <p>In your email program's menu, go to Enigmail &rarr; Key Management.</p>
 461                                                                 <p>Right click on Edward's public key and select Sign Key from the context menu.</p>
 462                                                                 <p>In the window that pops up, select "I will not answer" and click ok.</p>
 463                                                                 <p>Now you should be back at the Key Management menu. Select Keyserver &rarr; Upload Public Keys and hit ok.</p>
 464                                                                 <p class="notes">You've just effectively said "I trust that Edward's public key actually belongs to Edward." This doesn't mean much because Edward isn't a real person, but it's good practice.</p>
 465
 466
 467                                                                 <!--<div id="pgp-pathfinder">
 468                                                                 <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
 469                                                                 <p><strong>From:</strong> <input type="text" placeholder="xD41A008"  name="FROM"></p>
 470                                                                 <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
 471                                                                 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
 472                                                         </form>
 473                                                 </div>End #pgp-pathfinder -->
 474
 475                                         </div><!-- End .main -->
 476                                 </div><!-- End #step-4a .step -->
 477
 478                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 479                                 <div id="step-identify_keys" class="step">
 480                                         <div class="main">
 481                                                 <h3>Identifying keys: Fingerprints and IDs</h3>
 482                                                 <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Edward's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to Enigmail &rarr; Key Management in your email program's menu, then right clicking on the key and choosing Key Properties. It's good practice to share your fingerprint wherever you share your email address, so that people can double-check that they have the correct public key when they download yours from a keyserver.</p>
 483
 484                                                 <p class="notes">You may also see public keys referred to by their key ID, which is simply the last eight digits of the fingerprint, like C09A61E8 for Edward. The key ID is visible directly from the Key Management window. This key ID is like a person's first name (it is a useful shorthand but may not be unique to a given key), whereas the fingerprint actually identifies the key uniquely without the possibility of confusion. If you only have the key ID, you can still look up the key (as well as its fingerprint), like you did in Step 3, but if multiple options appear, you'll need the fingerprint of the person to whom you are trying to communicate to verify which one to use.</p>
 485
 486                                         </div><!-- End .main -->
 487                                 </div><!-- End #step-sign_real_keys .step-->
 488
 489                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 490                                 <div id="check-ids-before-signing" class="step">
 491                                         <div class="main">
 492                                                 <h3><em>Important:</em> What to consider when signing keys</h3>
 493                                                 <p>Before signing a person's key, you need to be confident that it actually belongs to them, and that they are who they say they are. Ideally, this confidence comes from having interactions and conversations with them over time, and witnessing interactions between them and others. Whenever signing a key, ask to see the full public key fingerprint, and not just the shorter key ID. If you feel it's important to sign the key of someone you've just met, also ask them to show you their government identification, and make sure the name on the ID matches the name on the public key. In Enigmail, answer honestly in the window that pops up and asks "How carefully have you verified that the key you are about to sign actually belongs to the person(s) named above?"
 494 </p>
 495
 496                                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 497                                                 <div class="troubleshooting">
 498                                                         <h4>Advanced</h4>
 499                                                         <dl>
 500                                                                 <dt>Master the Web of Trust</dt>
 501                                                                 <dd>Unfortunately, trust does not spread between users the way <a href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people think</a>. One of best ways to strengthen the GnuPG community is to deeply <a href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of Trust and to carefully sign as many people's keys as circumstances permit.</dd>
 502                                                                 <dt>Set ownertrust</dt>
 503                                                                 <dd>If you trust someone enough to validate other people's keys, you can assign them an ownertrust level through Enigmails's key management window. Right click on the other person's key, go to the "Select Owner Trust" menu option, select the trustlevel and click OK. Only do this once you feel you have a deep understanding of the Web of Trust.</dd>
 504                                                         </dl>
 505                                                 </div><!-- /.troubleshooting -->
 506                                         </div><!-- End .main -->
 507
 508                                 </div><!-- End #step-sign_real_keys .step-->
 509
 510
 511                         </div>
 512                 </section><!-- End #section4 -->
 513
 514                 <!-- ~~~~~~~~~ Section 5: Use it well  ~~~~~~~~~ -->
 515                 <section id="section5" class="row">
 516                         <div>
 517                                 <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 518                                 <div class="section-intro">
 519                                         <h2><em>#5</em> Use it well</h2>
 520                                         <p>Everyone uses GnuPG a little differently, but it's important to follow some basic practices to keep your email secure. Not following them, you risk the privacy of the people you communicate with, as well as your own, and damage the Web of Trust.</p>
 521                                 </div><!-- End .section-intro -->
 522
 523                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 524                                 <div id="step-5a" class="step">
 525                                         <div class="sidebar">
 526                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
 527                                         </div><!-- /.sidebar -->
 528                                         <div class="main">
 529                                                 <h3>When should I encrypt? When should I sign?</h3>
 530
 531                                                 <p>The more you can encrypt your messages, the better. If you only encrypt emails occasionally, each encrypted message could raise a red flag for surveillance systems. If all or most of your email is encrypted, people doing surveillance won't know where to start. That's not to say that only encrypting some of your email isn't helpful -- it's a great start and it makes bulk surveillance more difficult.</p>
 532                                                 <p>Unless you don't want to reveal your own identity (which requires other protective measures), there's no reason not to sign every message, whether or not you are encrypting. In addition to allowing those with GnuPG to verify that the message came from you, signing is a non-intrusive way to remind everyone that you use GnuPG and show support for secure communication. If you often send signed messages to people that aren't familiar with GnuPG, it's nice to also include a link to this guide in your standard email signature (the text kind, not the cryptographic kind).</p>
 533
 534                                         </div><!-- End .main -->
 535                                 </div><!-- End #step-5a .step -->
 536
 537                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 538                                 <div id="step-5b" class="step">
 539                                         <div class="sidebar">
 540                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
 541                                         </div><!-- /.sidebar -->
 542                                         <div class="main">
 543                                                 <h3>Be wary of invalid keys</h3>
 544                                                 <p>GnuPG makes email safer, but it's still important to watch out for invalid keys, which might have fallen into the wrong hands. Email encrypted with invalid keys might be readable by surveillance programs.</p>
 545                                                 <p>In your email program, go back to the first encrypted email that Edward sent you. Because Edward encrypted it with your public key, it will have a message from Enigmail at the top, which most likely says "Enigmail: Part of this message encrypted."</p>
 546                                                 <p><b>When using GnuPG, make a habit of glancing at that bar. The program will warn you there if you get an email encrypted with a key that can't be trusted.</b></p>
 547                                         </div><!-- End .main -->
 548                                 </div><!-- End #step-5b .step -->
 549
 550                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 551                                 <div id="step-5c" class="step">
 552                                         <div class="main">
 553                                                 <h3>Copy your revocation certificate to somewhere safe</h3>
 554                                                 <p>Remember when you created your keys and saved the revocation certificate that GnuPG made? It's time to copy that certificate onto the safest digital storage that you have -- the ideal thing is a flash drive, disk, or hard drive stored in a safe place in your home, not on a device you carry with you regularly.</p>
 555                                                 <p>If your private key ever gets lost or stolen, you'll need this certificate file to let people know that you are no longer using that keypair.</p>
 556                                         </div><!-- End .main -->
 557                                 </div><!-- End #step-5c .step -->
 558
 559                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 560                                 <div id="step-lost_key" class="step">
 561                                         <div class="main">
 562                                                 <h3><em>Important:</em> act swiftly if someone gets your private key</h3>
 563                                                 <p>If you lose your private key or someone else gets ahold of it (say, by stealing or cracking your computer), it's important to revoke it immediately before someone else uses it to read your encrypted email or forge your signature. This guide doesn't cover how to revoke a key, but you can follow these <a href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>. After you're done revoking, make a new key and send an email to everyone with whom you usually use your key to make sure they know, including a copy of your new key.</p>
 564                                         </div><!-- End .main -->
 565                                 </div><!-- End #step-lost_key .step-->
 566
 567
 568
 569                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 570                                 <!---<div id="transfer-key" class="step">
 571                                 <div class="main">
 572                                 <h3>Transferring you key</h3>
 573                                 <p>You can use Enigmail's <a href="https://www.enigmail.net/documentation/keyman.php">key management window</a> to import and export keys. If you want to be able to read your encrypted email on a different computer, you will need to export your secret key from here. Be warned, if you transfer the key without <a href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a> the drive it's on the transfer will be dramatically less secure.</p>
 574                         </div><!-- End .main -->
 575                 </div><!-- End #step-lost_key .step-->
 576
 577
 578
 579
 580                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 581                 <div id="webmail-and-GnuPG" class="step">
 582                         <div class="main">
 583                                 <h3>Webmail and GnuPG</h3>
 584                                 <p>When you use a web browser to access your email, you're using webmail, an email program stored on a distant website. Unlike webmail, your desktop email program runs on your own computer. Although webmail can't decrypt encrypted email, it will still display it in its encrypted form. If you primarily use webmail, you'll know to open your email client when you receive a scrambled email.</p>
 585                         </div><!-- End .main -->
 586                 </div><!-- End #step-lost_key .step-->
 587
 588                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~
 589                 <div id="step-5d" class="step">
 590                 <div class="main">
 591                 <h3>Make your public key part of your online identity</h3>
 592                 <p> First add your public key fingerprint to your email signature, then compose an email to at least five of your friends, telling them you just set up GnuPG and mentioning your public key fingerprint. Link to this guide and ask them to join you. Don't forget that there's also an awesome <a href="infographic.html">infographic to share.</a></p>
 593
 594                 <p class="notes">Start writing your public key fingerprint anywhere someone would see your email address: your social media profiles, blog, Website, or business card. (At the Free Software Foundation, we put ours on our <a href="https://fsf.org/about/staff">staff page</a>.) We need to get our culture to the point that we feel like something is missing when we see an email address without a public key fingerprint.</p>
 595         </div><!-- End .main
 596 </div> End #step-5d .step-->
 597
 598
 599 </div>
 600 </section><!-- End #section5 -->
 601
 602
 603
 604 <!-- ~~~~~~~~~ Section 6: Next steps  ~~~~~~~~~ -->
 605 <section class="row" id="section6">
 606         <div id="step-click_here" class="step">
 607                 <div class="main">
 608                         <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>
 609
 610                 </div><!-- End .main -->
 611         </div><!-- End #step-click_here .step-->
 612
 613 </section><!-- End #section6 -->
 614
 615 <!-- ~~~~~~~~~ FAQ  ~~~~~~~~~ -->
 616 <!-- When un-commenting this section go to main.css and search
 617 for /* Guide Sections Background */ then add #faq to the desired color
 618
 619 <section class="row" id="faq">
 620 <div>
 621 <div class="sidebar">
 622 <h2>FAQ</h2>
 623 </div>
 624
 625 <div class="main">
 626 <dl>
 627 <dt>My key expired</dt>
 628 <dd>Answer coming soon.</dd>
 629
 630 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
 631 <dd>Answer coming soon.</dd>
 632
 633 <dt>My email program is opening at times I don't want it to open/is now my default program and I don't want it to be.</dt>
 634 <dd>Answer coming soon.</dd>
 635 </dl>
 636 </div>
 637 </div>
 638 </section> --><!-- End #faq -->
 639
 640 <!-- ~~~~~~~~~ Footer  ~~~~~~~~~ -->
 641 <footer class="row" id="footer">
 642         <div>
 643                 <div id="copyright">
 644                         <h4><a href="https://u.fsf.org/ys"><img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" /></a></h4>
 645                         <p>Copyright &copy; 2014-2016 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please support our work by <a href="https://u.fsf.org/yr">joining us as an associate member.</a></p>
 646
 647                         <p>The images on this page are under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 license (or later version)</a>, and the rest of it is under a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons Attribution-ShareAlike 4.0 license (or later version)</a>. Download the <a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source code of Edward reply bot</a> by Andrew Engelbrecht &lt;sudoman@ninthfloor.org&gt; and Josh Drake &lt;zamnedix@gnu.org&gt;, available under the GNU Affero General Public License. <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
 648
 649                         <p>Fonts used in the guide &amp; infographic: <a href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo Impallari, <a href="http://www.google.com/fonts/specimen/Signika">Signika</a> by Anna Giedry&#347;, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> by Florian Cramer.</p>
 650
 651                         <p>Download the <a href="emailselfdefense_source.zip">source package</a> for this guide, including fonts, image source files and the text of Edward's messages.</p>
 652
 653                         <p>This site uses the Weblabels standard for labeling <a href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">source code and license information</a>.</p>
 654                 </div><!-- /#copyright -->
 655                 <p class="credits">
 656                         Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>
 657                 </p><!-- /.credits -->
 658         </div>
 659 </footer><!-- End #footer -->
 660
 661 <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
 662 <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
 663
 664 <!-- Piwik -->
 665 <script type="text/javascript" >
 666 // @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
 667 var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");
 668 document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
 669 try {
 670         var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);
 671         piwikTracker.trackPageView();
 672         piwikTracker.enableLinkTracking();
 673 } catch( err ) {}
 674 // @license-end
 675 </script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>
 676 <!-- End Piwik Tracking Code -->
 677
 678
 679
 680 </body>
 681 </html>