[enc.git] / en / index.html

<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Email Self-Defense - a guide to fighting surveillance with GnuPG
encryption</title>
<meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy,
email, security, GnuPG2, encryption" />
<meta name="description" content="Email surveillance violates our fundamental
rights and makes free speech risky. This guide will teach you email
self-defense in 40 minutes with GnuPG." />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link rel="stylesheet" href="../static/css/main.css" />
<link rel="shortcut icon"
href="../static/img/favicon.ico" />
</head>
<body>
<!--<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>-->

<!-- PLACE FUNDRAISER MODAL WINDOW HERE -->

<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
<header class="row" id="header"><div>


<h1>Email Self-Defense</h1>

<!-- Language list for browsers that do not have JS enabled -->
<ul id="languages" class="os">
<li><strong><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
Translate!</a></strong></li>
</ul>

<ul id="menu" class="os">
<li class="spacer"><a href="index.html" class="current">Set up guide</a></li>
<!--<li><a href="mac.html">Mac OS</a></li>-->
<!--<li><a href="windows.html">Windows</a></li>-->
<li class="spacer"><a href="workshops.html">Teach your friends</a></li>
<li class="spacer"><a
href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email%20encryption%20for%20everyone%20via%20%40fsf">
Share&nbsp;
<img src="../static/img/gnu-social.png" class="share-logo"
alt="[GNU Social]" />&nbsp;
<img src="../static/img/mastodon.png" class="share-logo"
alt="[Mastodon]" />&nbsp;
<img src="../static/img/reddit-alien.png" class="share-logo"
alt="[Reddit]" />&nbsp;
<img src="../static/img/hacker-news.png" class="share-logo"
alt="[Hacker News]" /></a></li>
</ul>

<!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
<div id="fsf-intro">

<h3><a href="https://u.fsf.org/ys"><img
alt="Free Software Foundation"
src="../static/img/fsf-logo.png" />
</a></h3>

<div class="fsf-emphasis">

<p>We fight for computer users' rights, and promote the development of free (as
in freedom) software. Resisting bulk surveillance is very important to us.</p>

<p><strong>Please donate to support Email Self-Defense. We need to keep
improving it, and making more materials, for the benefit of people around
the world taking the first step towards protecting their privacy.</strong></p>

</div>

<div style="text-align: center;">
<p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&amp;id=14&amp;mtm_campaign=email_self_defense&amp;mtm_kwd=guide_donate"><img alt="Donate" src="../static/img/en/donate.png" /></a></p>

<h5>Sign up</h5>
<form action="https://my.fsf.org/civicrm/profile/create?reset=1&gid=31" method="post">
<p>Enter your email address to receive our monthly newsletter, the<br><a href="https://www.fsf.org/free-software-supporter/">Free Software Supporter</a></p>

<p><input id="frmEmail" type="text" name="email-Primary" size="18" maxlength="80" /></p>
<p><input type="submit" name="_qf_Edit_next" value="Subscribe me" /></p>
<div><input name="postURL" type="hidden" value="" />
<input type="hidden" name="group[25]" value="1" />
<input name="cancelURL" type="hidden" value="https://my.fsf.org/civicrm/profile?reset=1&gid=31" />
<input name="_qf_default" type="hidden" value="Edit:cancel" />
</div>
</form></div>

</div><!-- End #fsf-intro -->

<!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
<div class="intro">

<p><a id="infographic" href="infographic.html"><img
src="../static/img/en/infographic-button.png"
alt="View &amp; share our infographic &rarr;" /></a>
Bulk surveillance violates our fundamental rights and makes free speech
risky. This guide will teach you a basic surveillance self-defense skill: email
encryption. Once you've finished, you'll be able to send and receive emails
that are scrambled to make sure a surveillance agent or thief intercepting
your email can't read them. All you need is a computer with an Internet
connection, an email account, and about forty minutes.</p>

<p>Even if you have nothing to hide, using encryption helps protect the privacy
of people you communicate with, and makes life difficult for bulk surveillance
systems. If you do have something important to hide, you're in good company;
these are the same tools that whistleblowers use to protect their identities
while shining light on human rights abuses, corruption, and other crimes.</p>

<p>In addition to using encryption, standing up
to surveillance requires fighting politically for a <a
href="https://gnu.org/philosophy/surveillance-vs-democracy.html">reduction
in the amount of data collected on us</a>, but the essential first step is
to protect yourself and make surveillance of your communication as difficult
as possible. This guide helps you do that. It is designed for beginners, but
if you already know the basics of GnuPG or are an experienced free software
user, you'll enjoy the advanced tips and the <a href="workshops.html">guide
to teaching your friends</a>.</p>

</div><!-- End .intro -->
</div></header><!-- End #header -->

<!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
<section class="row" id="section1"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">

<h2><em>#1</em> Get the pieces</h2>

<p class="notes">This guide relies on software which is <a
href="https://www.gnu.org/philosophy/free-sw.html">freely licensed</a>;
it's completely transparent and anyone can copy it or make their
own version. This makes it safer from surveillance than proprietary
software (like Windows or macOS). Learn more about free software at <a
href="https://u.fsf.org/ys">fsf.org</a>.</p>

<p>Most GNU/Linux operating systems come with GnuPG installed on them, so if you're running one of these systems, you don't have to download it. If you're running macOS or Windows, steps to download GnuPG are below. Before configuring your encryption setup with this guide, though, you'll need a desktop email program installed on your computer. Many GNU/Linux distributions have one installed already, such as Icedove, which may be under the alternate name "Thunderbird." Programs like these are another way to access the same email accounts you can access in a browser (like Gmail), but provide extra features.</p>

</div><!-- End .section-intro -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-1a" class="step">
<div class="sidebar">

<p class="large"><img
src="../static/img/en/screenshots/step1a-install-wizard.png"
alt="Step 1.A: Install Wizard" /></p>

</div><!-- /.sidebar -->
<div class="main">

<h3><em>Step 1.a</em> Set up your email program with your email account</h3>

<p>Open your email program and follow the wizard (step-by-step walkthrough)
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>


<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>Troubleshooting</h4>

<dl>
<dt>The wizard doesn't launch</dt>
<dd>You can launch the wizard yourself, but the menu option for doing so is
named differently in each email program. The button to launch it will be in
the program's main menu, under "New" or something similar, titled something
like "Add account" or "New/Existing email account."</dd>

<dt>The wizard can't find my account or isn't downloading my mail</dt>
<dd>Before searching the Web, we recommend you start by asking other people
who use your email system, to figure out the correct settings.</dd>

<dt>I can't find the menu</dt>
<dd>In many new email programs, the main menu is represented by an image of
three stacked horizontal bars.</dd>

<dt class="feedback">Don't see a solution to your problem?</dt>
<dd class="feedback">Please let us know on the <a
href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
page</a>.</dd>
</dl>

</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #step1-a .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-1b" class="step">
<div class="main">

<h3><em>Step 1.b</em> Install GnuPG</h3>

<p>If you are using a GNU/Linux machine, you should already have GnuPG installed, and you can skip to <a href="#section2">Section 2</a>.</p>

<p>If you are using a macOS or Windows machine, however, you need to first install the GnuPG program. Select your operating system below and follow the instructions. For the rest of this guide, the steps are the same for all operating systems. </p>

<!-- ~~~~~~~~~ MACOS ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>macOS</h4>

<dl>
<dt>Use a third-party package manager to install GnuPG</dt>
<dd>
<p>The default macOS package manager makes it difficult to install GnuPG and other pieces of free software (like Emacs, GIMP, or Inkscape). To make things easier, we recommend setting up the third-party package manager "Homebrew" to install GnuPG. For this, we will use a program called "Terminal," which is pre-installed on macOS.</p>

<p># Copy the first command on the home page of <a href="https://brew.sh/">Homebrew</a> by clicking on the clipboard icon, and paste it in Terminal. Click "Enter" and wait for the installation to finalize.</p>
<p># Then install GnuPG by entering the following code in Terminal:<br/>
<code>brew install gnupg gnupg2</code></p>
</dd>
</dl>

</div><!-- /.troubleshooting -->

<!-- ~~~~~~~~~ WINDOWS ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>Windows</h4>

<dl>
<dt>Get GnuPG by downloading GPG4Win</dt>
<dd><p><a href="https://www.gpg4win.org/">GPG4Win</a> is an email and file encryption software package that includes GnuPG. Download and install the latest version, choosing default options whenever asked. After it's installed, you can close any windows that it creates.</p>
</dd>
</dl>

</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #step1-b .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="terminology" class="step">
<div class="main">

<h3>GnuPG, OpenPGP, what?</h3>

<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. Most email programs provide an interface for GnuPG. There is also a newer version of GnuPG, called GnuPG2.</p>

</div><!-- End .main -->
</div><!-- End #terminology.step-->

</div></section><!-- End #section1 -->

<!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
<section id="section2" class="row"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">

<h2><em>#2</em> Make your keys</h2>
<p class="float medium"><img src="../static/img/en/screenshots/step2a-01-make-keypair.png" alt="A robot with a head shaped like a key holding a private and a public key"/></p>

<p>To use the GnuPG system, you'll need a public key and a private key (known
together as a keypair). Each is a long string of randomly generated numbers
and letters that are unique to you. Your public and private keys are linked
together by a special mathematical function.</p>

<p>Your public key isn't like a physical key, because it's stored in the open
in an online directory called a keyserver. People download it and use it,
along with GnuPG, to encrypt emails they send to you. You can think of the
keyserver as a phonebook; people who want to send you encrypted email can
look up your public key.</p>

<p>Your private key is more like a physical key, because you keep it to
yourself (on your computer). You use GnuPG and your private key together to
descramble encrypted emails other people send to you. <strong>You should never share your private key with anyone, under any
circumstances.</strong></p>

<p>In addition to encryption and decryption, you can also use these keys to
sign messages and check the authenticity of other people's signatures. We'll
discuss this more in the next section.</p>

</div><!-- End .section-intro -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-2a" class="step">
<div class="sidebar">
<p class="large"><img
src="../static/img/en/screenshots/step2a-02-make-keypair.png"
alt="Step 2.A: Make your Keypair" /></p>

<p class="large"><img
src="../static/img/en/screenshots/step2a-03-make-keypair.png"
alt="Step 2.A: Set your passphrase" /></p>

</div><!-- /.sidebar -->
<div class="main">

<h3><em>Step 2.a</em> Make a keypair</h3>

<h4>Make your keypair</h4>

<p>We will use the command line in a terminal to create a keypair using the
GnuPG program.</p>

<p class="notes">Whether on GNU/Linux, macOS or Windows, you can launch your
terminal ("Terminal" in macOS, "PowerShell" in Windows) from the Applications
menu (some GNU/Linux systems respond to the <kbd>Ctrl + Alt + T</kbd>
shortcut).</p>

<p># Enter <code>gpg --full-generate-key</code> to start the process.</p>
<p># To answer what kind of key you would like to create, select the default option: <samp>1&nbsp;RSA&nbsp;and&nbsp;RSA</samp>.</p>
<p># Enter the following keysize: <code>4096</code> for a strong key.</p>
<p># Choose the expiration date; we suggest <code>2y</code> (2 years).</p>
<p>Follow the prompts to continue setting up with your personal details.</p>
<p class="notes"> Depending on your version of GPG, you may need to use
<code>--gen-key</code> instead of <code>--full-generate-key</code>&#65279;.</p>

<h4>Set your passphrase</h4>
<p>On the screen titled "Passphrase," 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 to 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>


<p>If you'd like to pick a passphrase 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>

<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>Troubleshooting</h4>
<dl>
<dt>GnuPG is not installed</dt>
<dd>
You can check if this is the case with the command <code>gpg --version</code>&#65279;.
If GnuPG is not installed, it will bring up the following result on most GNU/Linux operating systems, or something like it:
<samp>Command 'gpg' not found, but can be installed with:
  sudo apt install gnupg</samp>. Follow that command and install the program.</dd>

<dt><i>gpg --full-generate-key</i> command not working</dt>
<dd>Some distributions use a different version of GPG. When you receive an error code that is something along the lines of: <samp>gpg: Invalid option "--full-generate-key"</samp>, you can try the following commands: <br /> 
<code>sudo apt update</code><br />
<code>sudo apt install gnupg2</code><br />
<code>gpg2 --full-generate-key</code><br />
If this resolved the issue, you need to continue to use the gpg2 identifier instead of gpg throughout the following steps of the guide.
<p class="notes"> Depending on your version of GPG, you may need to use
<code>--gen-key</code> instead of <code>--full-generate-key</code>&#65279;.</p>
</dd>

<dt>I took too long to create my passphrase</dt>
<dd>That's okay. It's important to think about your passphrase. When you're ready, just follow the steps from the beginning again to create your key.</dd>

<dt>How can I see my key?</dt>
<dd>
Use the following command to see all keys: <code>gpg --list-keys</code>&#65279;. Yours should be listed in there, and later, so will Edward's (<a href="#section3">Section 3</a>).<br />
If you want to see only your key, you can use <code>gpg --list-key [your@email]</code>&#65279;.<br />
You can also use <code>gpg --list-secret-key</code> to see your own private key.</dd>

<dt>More resources</dt>
<dd>For more information about this process, you can also refer to <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 4096&nbsp;bits if you
want to be secure.</dd>

<dt class="feedback">Don't see a solution to your problem?</dt>
<dd class="feedback">Please let us know on the <a
href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
page</a>.</dd>
</dl>

</div><!-- /.troubleshooting -->

<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>Advanced</h4>
<dl>
<dt>Advanced key pairs</dt>
<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 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="https://keyring.debian.org/creating-key.html">the Debian wiki</a>
provide good guides for setting up a secure subkey configuration.</dd>
</dl>

</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #step-2a .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-2b" class="step">
<div class="sidebar">
<p class="large"><img
src="../static/img/en/screenshots/step2b-04-upload-and-certificate.png"
alt="Step 2.B: Send to server and generate a certificate" /></p>

</div><!-- /.sidebar -->
<div class="main">

<h3><em>Step 2.b</em> Some important steps following creation</h3>

<h4>Upload your key to a keyserver</h4>
<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
that you can select from the menu when you upload, but they are mostly all copies
of each other. Any server will work, but it's good to remember which one you uploaded your key to originally. Also keep in mind, sometimes takes a few hours for them to match each other when a new key is uploaded.</p>
<p># Copy your keyID: <code>gpg --list-key [your@email]</code> will list your public ("pub") key information, including your keyID, which is a unique list of numbers and letters. Copy this keyID, so you can use it in the following command.</p>
<p># Upload your key to a server:
<code>gpg --send-key [keyID]</code></p>

<h4>Export your key to a file</h4>
<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>
<p><code>
$ gpg --export-secret-keys -a [keyID] > my_secret_key.asc<br/>
$ gpg --export -a [keyID] > my_public_key.asc
</code></p>

<h4>Generate a revocation certificate</h4>
<p>Just in case you lose your key, or it gets compromised, you want to generate a certificate  and choose to save it in a safe place on your computer for now (please refer to <a href="#step-6c">Step 6.C</a> for how to best store your revocation cerficate safely). This step is essential for your email self-defense, as you'll learn more about in <a href="#section5">Section 5</a>.</p> 
 
<p># Copy your keyID: <code>gpg --list-key [your@email]</code> will list your public ("pub") key information, including your keyID, which is a unique list of numbers and letters. Copy this keyID, so you can use it in the following command.</p>
<p># Generate a revocation certificate: <code>gpg --gen-revoke --output revoke.asc [keyID]</code></p>
<p># It will prompt you to give a reason for revocation, we recommend to use <samp>1&nbsp;=&nbsp;key has been compromised</samp>.</p>
<p># You don't have to fill in a reason, but you can; then press "Enter" for an empty line, and confirm your selection.</p>


<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>Troubleshooting</h4>

<dl>
<dt>Sending my key to the keyserver is not working</dt>
<dd>Instead of using the general command to upload your key to the keyserver, you can use a more specific command and add the keyserver to your command <code>gpg --keyserver keys.openpgp.org --send-key [keyID]</code>&#65279;.</dd>

<dt>My key doesn't seem to be working or I get a "permission denied."</dt>
<dd><p>Like every other file or folder, gpg keys are subject to permissions. If these are not set correctly, your system may not be accepting your keys. You can follow the next steps to check, and update to the right permissions.</p>

<p># Check your permissions: <code>ls -l ~/.gnupg/*</code></p>
<p># Set permissions to read, write, execute for only yourself, no others. These are the recommended permissions for your folder. <br/>
You can use the code: <code>chmod 700 ~/.gnupg</code></p>
<p># Set permissions to read and write for yourself only, no others. These are the recommended permissions for the keys inside your folder. <br/>
You can use the code: <code>chmod 600 ~/.gnupg/*</code></p>

<p class="notes">If you have (for any reason) created your own folders inside ~/.gnupg, you must also additionally apply execute permissions to that folder. Folders require execution privileges to be opened. For more information on permissions, you can check out <a href="https://helpdeskgeek.com/linux-tips/understanding-linux-permissions-chmod-usage/">this detailed information guide</a>.</p>
</dd>

<dt class="feedback">Don't see a solution to your problem?</dt>
<dd class="feedback">Please let us know on the <a
href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
page</a>.</dd>
</dl>

</div><!-- /.troubleshooting -->

<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>Advanced</h4>

<dl>
<dt>More about keyservers</dt>
<dd>You can find some more keyserver information<a
href="https://www.gnupg.org/gph/en/manual/x457.html"> in this manual</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>

<dt>Transferring your keys</dt>
<dd>
<p>Use the following commands to transfer your keys. To avoid getting your key compromised, store it in a safe place, and make sure that if it is transferred, it is done so in a trusted way. Importing and exporting a key can be done with the following commands:</p>

<p><code>
$ gpg --export-secret-keys -a [keyID] > my_private_key.asc<br />
$ gpg --export -a [keyID] > my_public_key.asc<br />
$ gpg --import my_private_key.asc<br />
$ gpg --import my_public_key.asc
</code></p>

<p>Ensure that the keyID printed is the correct one, and if so, then go ahead and add ultimate trust for it:</p>

<p><code>
$ gpg --edit-key [your@email]
</code></p>

<p>Because this is your key, you should choose <code>ultimate</code>&#65279;. You shouldn't trust anyone else's key ultimately.</p>

<p class="notes"> Refer to <a href="#step-2b">Troubleshooting in Step 2.B</a> for more information on permissions. When transferring keys, your permissions may get mixed, and errors may be prompted. These are easily avoided when your folders and files have the right permissions</p>
</dd>
</dl>

</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #step-2b .step -->
</div></section><!-- End #section2 -->

<!-- ~~~~~~~~~ Section 3: Set up email encryption ~~~~~~~~~ -->
<section id="section3" class="row"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">

<h2><em>#3</em> Set up email encryption</h2>
<p class="notes">The Icedove (or Thunderbird) email program has PGP functionality integrated, which makes it pretty easy to work with. We'll take you through the steps of integrating and using your key in these email clients.</p>

</div><!-- End .section-intro -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-3a" class="step">
<div class="sidebar">

<p class="large"><img src="../static/img/en/screenshots/step3a-open-key-manager.png"
alt="Step 3.A: Email Menu" /></p>

<p class="large"><img src="../static/img/en/screenshots/step3a-import-from-file.png"
alt="Step 3.A: Import From File" /></p>

<p class="large"><img src="../static/img/en/screenshots/step3a-success.png"
alt="Step 3.A: Success" /></p>

<p class="large"><img src="../static/img/en/screenshots/step3a-troubleshoot.png"
alt="Step 3.A: Troubleshoot" /></p>
</div><!-- /.sidebar -->
<div class="main">

<h3><em>Step 3.a</em> Set up your email with encryption</h3>

<p>Once you have set up your email with encryption, you can start contributing to encrypted traffic on the Internet. First we'll get your email client to import your secret key, and we will also learn how to get other people's public keys from servers so you can send and receive encrypted email.</p>

<p># Open your email client and use "Tools" &rarr; <i>OpenPGP Key Manager</i></p>
<p># Under "File" &rarr; <i>Import Secret Key(s) From File</i></p>
<p># Select the file you saved under the name [my_secret_key.asc] in <a href="#step-2b">Step 2.B</a> when you exported your key</p>
<p># Unlock with your passphrase</p>
<p># You will receive a "OpenPGP keys successfully imported" window to confirm success</p>
<p># Go to "Account settings" &rarr; "End-To-End Encryption," and make sure your key is imported and select <i>Treat this key as a Personal Key</i>.</p>

</div><!-- End .main -->

<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="main">
<div class="troubleshooting">
<h4>Troubleshooting</h4>
<dl>
<dt>I'm not sure the import worked correctly</dt>
<dd>
Look for "Account settings" &rarr; "End-To-End Encryption." Here you can see if your personal key associated with this email is found. If it is not, you can try again via the <i>Add key</i> option. Make sure you have the correct, active, secret key file.
</dd>

<dt class="feedback">Don't see a solution to your problem?</dt>
<dd class="feedback">Please let us know on the <a
href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
page</a>.</dd>
</dl>

</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #step3-a .step -->
</div></section><!-- End #section3 -->

<!-- ~~~~~~~~~ Section 4: Try it out ~~~~~~~~~ -->
<section class="row" id="section4"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">

<h2><em>#4</em> Try it out!</h2>
<p class="float small"><img src="../static/img/en/screenshots/section3-try-it-out.png" alt="Illustration of a person in a house with a cat connected to a server"/></p>
<p>Now you'll try a test correspondence with an FSF 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>

<!-- <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> -->

<div style="clear: both"></div>
</div><!-- End .section-intro -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-4a" class="step">
<div class="sidebar">

<p class="large"><img
src="../static/img/en/screenshots/step4a-send-key-to-Edward.png"
alt="Step 4.A Send key to Edward." /></p>

</div><!-- /.sidebar -->
<div class="main">

<h3><em>Step 4.a</em> Send Edward your public key</h3>

<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 "Tools" &rarr; "OpenPGP Key
Manager." You should see your key in the list that pops up. Right click
on your key and select <i>Send Public Keys by Email</i>. This will create a new draft message, as if you had just hit the "Write" button, but in the attachment you will find your public keyfile.</p>

<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>

<p>We want Edward to be able to open the email with your keyfile, so we want this first special message to be unencrypted. Make sure encryption is turned off by using the dropdown menu "Security" and select <i>Do Not Encrypt</i>. Once encryption is off, hit Send.</p>

<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="#section6">Use it Well</a> section of this guide. Once you have received a response,
head to the next step. From here on, you'll be doing just the same thing as
when corresponding with a real person.</p>

<p>When you open Edward's reply, GnuPG may prompt you for your passphrase
before using your private key to decrypt it.</p>

</div><!-- End .main -->
</div><!-- End #step-4a .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-4b" class="step">
<div class="sidebar">

<p class="large"><img
src="../static/img/en/screenshots/step4b-option1-verify-key.png"
alt="Step 4.B Option 1. Verify key" /></p>

<p class="large"><img
src="../static/img/en/screenshots/step4b-option2-import-key.png"
alt="Step 4.B Option 2. Import key" /></p>
</div><!-- /.sidebar -->

<div class="main">

<h3><em>Step 4.b</em> Send a test encrypted email</h3>

<h4>Get Edward's key</h4>

<p>To encrypt an email to Edward, you need its public key, so now you'll have
to download it from a keyserver. You can do this in two different ways:</p>
<p><strong>Option 1.</strong> In the email answer you received from Edward as a response to your first email, Edward's public key was included. On the right of the email, just above the writing area, you will find an "OpenPGP" button that has a lock and a little wheel next to it. Click that, and select <i>Discover</i> next to the text: "This message was signed with a key that you don't yet have." A popup with Edward's key details will follow.</p>

<p><strong>Option 2.</strong> Open your OpenPGP Key manager, and under "Keyserver" choose <i>Discover Keys Online</i>. Here, fill in Edward's email address, and import Edward's key.</p>

<p>The option <i>Accepted (unverified)</i> will add this key to your key manager, and now it can be used to send encrypted emails and to verify digital signatures from Edward.</p>

<p class="notes">In the popup window confirming if you want to import Edward's key, you'll see many  different emails that are all associated with its key. This is correct; you can safely import the key.</p>

<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
its private key, so no one except Edward can decrypt it.</p>

<h4>Send Edward an encrypted email</h4>

<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>

<p>This time, make sure encryption is turned on by using the dropdown menu "Security" and select <i>Require Encryption</i>. Once encryption is on, hit Send.</p>


<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>Troubleshooting</h4>

<dl>
<dt>"Recipients not valid, not trusted or not found"</dt>
<dd>You could get the above error message, or something along these lines:  "Unable to send this message with end-to-end encryption, because there are problems with the keys of the following recipients: ..." In these cases, you may be trying to send an encrypted email to someone when you do not have their public key yet. Make sure you follow the steps above to import the key to your key manager. Open the OpenPGP Key Manager to make sure the recipient is listed there.</dd>

<dt>Unable to send message</dt>
<dd>You could get the following message when trying to send your encrypted email: "Unable to send this message with end-to-end encryption, because there are problems with the keys of the following recipients: edward-en@fsf.org." This usually means you imported the key with the "unaccepted (unverified) option." Go to the "key properties" of this key by right clicking on the key in the OpenPGP Key Manager, and select the option <i>Yes, but I have not verified that this is the correct key</i> in the "Acceptance" option at the bottom of this window. Resend the email.</dd>

<dt>I can't find Edward's key</dt>
<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, you can download the key manually from <a href="https://keys.openpgp.org/search?q=edward-en%40fsf.org">the keyserver</a>, and import it by using the <i>Import Public Key(s) from File</i> option in the OpenPGP Key Manager.</dd>

<dt>Unscrambled messages in the Sent folder</dt>
<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>

<dt class="feedback">Don't see a solution to your problem?</dt>
<dd class="feedback">Please let us know on the <a
href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback
page</a>.</dd>
</dl>

</div><!-- /.troubleshooting -->

<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>Advanced</h4>

<dl>
<dt>Encrypt messages from the command line</dt>
<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>
</dl>

</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #step-4b .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-headers_unencrypted" class="step">
<div class="main">

<h3><em>Important:</em> Security tips</h3>

<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, you can choose to encrypt them or not,
independent of the actual email.</p>

<p>For greater security against potential attacks, you can turn off
HTML. Instead, you can render the message body as plain text. In order
to do this in Icedove or Thunderbird, go to "View" &rarr; "Message Body As" &rarr; <i>Plain
Text</i>.</p>

</div><!-- End .main -->
</div><!-- End #step-headers_unencrypted .step-->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-4c" class="step">
<div class="sidebar">

<p class="large"><img
src="../static/img/en/screenshots/step4c-Edward-response.png"
alt="Step 4.C Edward's response" /></p>

</div><!-- /.sidebar -->

<div class="main">

<h3><em>Step 4.c</em> Receive a response</h3>

<p>When Edward receives your email, it will use its private key to decrypt
it, then reply to you. </p>

<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="#section6">Use it Well</a> section of this guide.</p>

<p>Edward will send you an encrypted email back saying your email was received and decrypted. Your email client will automatically decrypt Edward's message.</p>

<p class="notes">The OpenPGP button in the email will show a little green checkmark over the lock symbol to show the message is encrypted, and a little orange warning sign which means that you have accepted the key, but not verified it. When you have not yet accepted the key, you will see a little question mark there. Clicking the prompts in this button will lead you to key properties as well.</p>

</div><!-- End .main -->
</div><!-- End #step-4c .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-4d" class="step">
<div class="main">

<h3><em>Step 4.d</em> Send a signed test email</h3>

<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>

<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>

<p>To sign an email to Edward, compose any message to the email address 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>

<p>In "Account Settings" &rarr; "End-To-End-Encryption" you can opt to <i>add digital signature by default</i>.</p>

</div><!-- End .main -->
</div><!-- End #step-4d .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-4e" class="step">
<div class="main">

<h3><em>Step 4.e</em> Receive a response</h3>

<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 the message
you sent has not been tampered with and to encrypt a reply to you.</p>

<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="#section6">Use it Well</a> section of this guide.</p>

<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>

<p>When you receive Edward's email and open it, your email client will
automatically detect that it is encrypted with your public key, and
then it will use your private key to decrypt it.</p>

</div><!-- End .main -->
</div><!-- End #step-4e .step -->
</div></section>

<!-- ~~~~~~~~~ Section 5: Learn About the Web of Trust ~~~~~~~~~ -->
<section class="row" id="section5"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">

<h2><em>#5</em> Learn about the Web of Trust</h2>
<p class="float small"><img src="../static/img/en/screenshots/section5-web-of-trust.png" alt="Illustration of keys all interconnected with a web of lines"/></p>

<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>

<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>

<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 accidentally end up vouching for the identity of an imposter.</p>

<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>

</div><!-- End .section-intro -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-5a" class="step">
<div class="sidebar">

<p class="large"><img
src="../static/img/en/screenshots/step5a-key-properties.png"
alt="Section 5: trusting a key" /></p>

</div><!-- /.sidebar -->
<div class="main">

<h3><em>Step 5.a</em> Sign a key</h3>

<p>In your email program's menu, go to OpenPGP Key Manager and select <i>Key properties</i> by right clicking on Edward's key.</p>

<p>Under "Your Acceptance," you can select <i>Yes, I've verified in person this key has the correct fingerprint"</i>.</p>

<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, 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>

<!--<div id="pgp-pathfinder">

<form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi"
method="get">

<p><strong>From:</strong><input type="text" value="xD41A008"
name="FROM"></p>

<p><strong>To:</strong><input type="text" value="50BD01x4" name="TO"></p>

<p class="buttons"><input type="submit" value="trust paths" name="PATHS"><input
type="reset" value="reset" name=".reset"></p>

</form>

</div>End #pgp-pathfinder -->
</div><!-- End .main -->
</div><!-- End #step-5a .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-identify_keys" class="step">
<div class="main">

<h3>Identifying keys: Fingerprints and IDs</h3>

<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 OpenPGP 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>

<p class="notes">You may also see public keys referred to by a shorter
keyID. This keyID is visible directly from the Key Management
window. These eight character keyIDs were previously used for
identification, which used to be safe, but is no longer reliable. You
need to check the full fingerprint as part of verifying you have the
correct key for the person you are trying to contact. Spoofing, in
which someone intentionally generates a key with a fingerprint whose
final eight characters are the same as another, is unfortunately
common.</p>

</div><!-- End .main -->
</div><!-- End #step-identify_keys .step-->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="check-ids-before-signing" class="step">
<div class="main">

<h3><em>Important:</em> What to consider when signing keys</h3>

<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
keyID. 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.</p>

<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">

<h4>Advanced</h4>

<dl>
<dt>Master the Web of Trust</dt>
<dd>Unfortunately, trust does not spread between users the way <a
href="https://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people
think</a>. One of the 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>
</dl>

</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #check-ids-before-signing .step-->
</div></section><!-- End #section5 -->

<!-- ~~~~~~~~~ Section 6: Use it well ~~~~~~~~~ -->
<section id="section6" class="row"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">

<h2><em>#6</em> Use it well</h2>

<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>

</div><!-- End .section-intro -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-6a" class="step">
<div class="sidebar">

<p class="medium"><img
src="../static/img/en/screenshots/section6-01-use-it-well.png"
alt="Section 6: Use it Well (1)" /></p>

</div><!-- /.sidebar -->
<div class="main">

<h3>When should I encrypt? When should I sign?</h3>

<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>

<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>

</div><!-- End .main -->
</div><!-- End #step-6a .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-6b" class="step">
<div class="sidebar">

<p class="medium"><img
src="../static/img/en/screenshots/section6-02-use-it-well.png"
alt="Section 6: Use it Well (2)" /></p>

</div><!-- /.sidebar -->
<div class="main">

<h3>Be wary of invalid keys</h3>

<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>

<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
green checkmark a at the top "OpenPGP" button.</p>

<p><strong>When using GnuPG, make a habit of glancing at that button. The program
will warn you there if you get an email signed with a key that can't
be trusted.</strong></p>

</div><!-- End .main -->
</div><!-- End #step-6b .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-6c" class="step">
<div class="main">

<h3>Copy your revocation certificate to somewhere safe</h3>

<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 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>

<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>

</div><!-- End .main -->
</div><!-- End #step-6c .step -->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-lost_key" class="step">
<div class="main">

<h3><em>IMPORTANT:</em> ACT SWIFTLY if someone gets your private key</h3>

<p>If you lose your private key or someone else gets a hold
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>

</div><!-- End .main -->
</div><!-- End #step-lost_key .step-->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="webmail-and-GnuPG" class="step">
<div class="main">

<h3>Webmail and GnuPG</h3>

<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>

</div><!-- End .main -->
</div><!-- End #webmail-and-GnuPG .step-->

<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-6d" class="step">
<div class="main">

<h3>Make your public key part of your online identity</h3>

<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>

<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>

</div><!-- End .main-->
</div><!-- End #step-6d .step-->
</div></section><!-- End #section6 -->

<!-- ~~~~~~~~~ Section 7: Next steps ~~~~~~~~~ -->
<section class="row" id="section7">
<div id="step-click_here" class="step">
<div class="main">

<h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>

</div><!-- End .main -->
</div><!-- End #step-click_here .step-->
</section><!-- End #section7 -->

<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
<!-- When un-commenting this section go to main.css and search
for /* Guide Sections Background */ then add #faq to the desired color
<section class="row" id="faq"><div>
<div class="sidebar">

<h2>FAQ</h2>

</div>
<div class="main">

<dl>
<dt>My key expired</dt>
<dd>Answer coming soon.</dd>

<dt>Who can read encrypted messages? Who can read signed ones?</dt>
<dd>Answer coming soon.</dd>

<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>
<dd>Answer coming soon.</dd>
</dl>

</div>
</div>
</section> --><!-- End #faq -->

<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
<footer class="row" id="footer"><div>
<div id="copyright">

<h4><a href="https://u.fsf.org/ys"><img
alt="Free Software Foundation"
src="../static/img/fsf-logo.png" /></a></h4>

<p>Copyright &copy; 2014-2021 <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>

<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="https://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
source code of Edward reply bot</a> by Andrew Engelbrecht
&lt;andrew@engelbrecht.io&gt; and Josh Drake &lt;zamnedix@gnu.org&gt;,
available under the GNU Affero General Public License. <a
href="https://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these
licenses?</a></p>

<p>Fonts used in the guide &amp; infographic: <a
href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo
Impallari, <a href="https://www.google.com/fonts/specimen/Signika">Signika</a>
by Anna Giedry&#347;, <a
href="https://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>

<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>

<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="https://weblabels.fsf.org/emailselfdefense.fsf.org/"
rel="jslicense">source code and license information</a>.</p>

</div><!-- /#copyright -->

<p class="credits">Infographic and guide design by <a rel="external"
href="https://jplusplus.org"><strong>Journalism++</strong><img
src="static/img/jplusplus.png"
alt="Journalism++" /></a></p><!-- /.credits -->
</div></footer><!-- End #footer -->


<script type="text/javascript"
src="../static/js/jquery-1.11.0.min.js"></script>
<script type="text/javascript"
src="../static/js/scripts.js"></script>
<!-- Piwik -->
<script type="text/javascript">
  // @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&amp;dn=gpl-2.0.txt GPL-2.0-or-later
  var _paq = _paq || [];
  _paq.push(["trackPageView"]);
  _paq.push(["enableLinkTracking"]);

  (function() {
    var u = (("https:" == document.location.protocol) ? "https" : "http") + "://"+"piwik.fsf.org//";
    _paq.push(["setTrackerUrl", u+"piwik.php"]);
    _paq.push(["setSiteId", "13"]);
    var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
    g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
  })();
  // @license-end
</script>
<!-- End Piwik Code -->
<!-- Piwik Image Tracker -->
<noscript><img src="https://piwik.fsf.org//piwik.php?idsite=13&amp;rec=1" style="border:0" alt="" /></noscript>
<!-- End Piwik -->
</body>
</html>