<title>Email Self-Defense - a guide to fighting surveillance with GnuPG
encryption</title>
<meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy,
-email, Enigmail" />
+email, security, GnuPG2" />
<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." />
href="https://u.fsf.org/ys">fsf.org</a>.</p>
<p>Most GNU/Linux operating systems come with GnuPG installed on them,
-so you don't have to download it. Before configuring your encryption setup with this guide, though, you'll need a desktop email program based on Thunderbird installed on your computer. Many GNU/Linux distributions have Thunderbird installed already. If you're using a [fully free distribution of GNU/Linux](https://www.gnu.org/distros/free-distros.html), we recommend installing "Icedove" instead. Programs like these are another way to access the same email accounts you can access in a browser (like Gmail), but provide extra features.</p>
+so you don't have to download it. Before configuring your encryption setup with this guide, though, you'll need a desktop email program based on Thunderbird installed on your computer. Many GNU/Linux distributions have Thunderbird installed already. If you're using a <a href="https://www.gnu.org/distros/free-distros.html">fully free distribution of GNU/Linux</a>, we recommend installing "Icedove" instead. Programs like these are another way to access the same email accounts you can access in a browser (like Gmail), but provide extra features.</p>
<p>If you already have an email program, you can skip to <a
-href="#step-1b">Step 1.b</a>.</p>
+href="#section2">Step 2</a>.</p>
</div><!-- End .section-intro -->
<div class="sidebar">
<p><img
-src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png"
+src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step1a-install-wizard.png"
alt="Step 1.A: Install Wizard" /></p>
</div><!-- /.sidebar -->
<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 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="sidebar">
-<ul class="images">
-<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>
-<li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png"
-alt="Step 1.B: Search Add-ons" /></li>
-<li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png"
-alt="Step 1.B: Install Add-ons" /></li>
-</ul>
-
-</div><!-- /.sidebar -->
-<div class="main">
-
-<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
-<div class="troubleshooting">
-
-<h4>Troubleshooting</h4>
-
-<dl>
<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>
</div><!-- /.troubleshooting -->
</div><!-- End .main -->
-</div><!-- End #step-1b .step -->
+</div><!-- End #step1-a .step -->
</div></section><!-- End #section1 -->
<!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
-<section
class="row" id="section2"><div>
+<section
id="section2" class="row"><div>
<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">
<h2><em>#2</em> Make your keys</h2>
+<p><img style="float:right; width:400px; margin-bottom:20px;" src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="A robot with a head shaped like a key holding a private and a public key"/></p>
<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
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-2a" class="step">
<div class="sidebar">
-
<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>
+src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step2a-02-make-keypair.png"
+alt="Step 2.A: Make your Keypair" text="Make a keypair" /></p>
+<br />
+<p><img
+src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step2a-03-make-keypair.png"
+alt="Step 2.A: Set your passphrase" /></p>
+<br />
</div><!-- /.sidebar -->
<div class="main">
<h3><em>Step 2.a</em> Make a keypair</h3>
-
+<h6>Make your keypair</h6>
<p>We will use the command line to create a keypair using the gnupg program. This should be installed on your Gnu/Linux operating system.
-Open a terminal using <text style= "color:#2f5faa">ctrl + alt + t</text> and use the following code to create your keypair:</p>
+Open a terminal using <text style="color:#2f5faa; font-family: monospace;">ctrl + alt + t</text>, or find it in your applications, and use the following code to create your keypair:</p>
-<p><text style="color:#2f5faa">gpg --full-generate-key</text> to start the process.</p>
-<p>To answer what kind of key you would like to create, select the default option <text style="color:#2f5faa"> 1 RSA and RSA<text>.</p>
-<p>Enter the following keysize: <text style="color:#2f5faa">4096</text></p>
-<p>Choose the expiration date, we suggest <text style="color:#2f5faa">2y</text>.</p>
+<p># <text style="color:#2f5faa; font-family: monospace;">gpg --full-generate-key</text> to start the process.</p>
+<p># To answer what kind of key you would like to create, select the default option <text style="color:#2f5faa; font-family: monospace;"> 1 RSA and RSA<text>.</p>
+<p># Enter the following keysize: <text style="color:#2f5faa; font-family: monospace;">4096</text> for a strong key.</p>
+<p># Choose the expiration date, we suggest <text style="color:#2f5faa; font-family: monospace;">2y</text> (2 years).</p>
<p>Follow the prompts to continue setting up with your personal details.</p>
-<img src="create-key.png">
-
-- What does RSA mean -
-- Why the 4096 keysize -
-
-<li>On the screen titled "Passphrase," pick a strong password! You can
+<br />
+<h6>Set your passphrase</h6>
+<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.</li>
-</ul>
+this article</a> by Micah Lee.</p>
+
-<p>If you'd like to pick a password manually, come up with something
+<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>
-
-
-<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>
+<br />
<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">
<h4>Troubleshooting</h4>
-
<dl>
<dt>GnuPG is not installed</dt>
-<dd><p class = "notes">
- <p>GPG is not installed. You can check if this is the case with
- <p>gnupg --version
- <p>If Gnupg is not installed, it would bring up the following result:
- <p>Command 'gpg' not found, but can be installed with:
- sudo apt install gnupg
- <p>Then follow that command and install the program:
- sudo apt install gnupg gnupg2</p></dd>
-
-<dt>I can't find the Enigmail menu.</dt>
-<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>
-
-<dt>The wizard says that it cannot find GnuPG.</dt>
-<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 → Setup Wizard.</dd>
+<dd>
+GPG is not installed. You can check if this is the case with the command <text style="color:#2f5faa; font-family: monospace;">gnupg --version</text>
+If Gnupg is not installed, it would bring up the following result:
+<text style="color:#2f5faa; font-family: monospace;">Command 'gpg' not found, but can be installed with:
+ sudo apt install gnupg</text>. Follow that command and install the program.</dd>
+
+<dt>I took too long to create my passphrase</dt>
+<dd>That's ok. It's important to think about your passphrase, when you're ready, just follow the steps to create your key again.</dd>
+
+<dt>How can i see my key?</dt>
+<dd>
+Use the following command to see all keys <text style="color:#2f5faa; font-family: monospace;">gnupg --list-keys</text>. Yours should be listed in there, and later, so will Edward's (step 3). If you want to see only your key, you can use <text style="color:#2f5faa; font-family: monospace;">gnupg --list-key [your@email]</text>
+You can also use <text style="color:#2f5faa; font-family: monospace;">gnupg --list-secret-key</text> to see your own private key.</dd>
<dt>More resources</dt>
-<dd>If you're having trouble with our
-instructions or just want to learn more, check out <a
-href="https://www.enigmail.net/documentation/Key_Management#Generating_your_own_key_pair">
-Enigmail's wiki instructions for key generation</a>.</dd>
+<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 2048 bits, or 4096 if you
+want to be extra secure.</dd>
<dt class="feedback">Don't see a solution to your problem?</dt>
<dd class="feedback">Please let us know on the <a
<div class="troubleshooting">
<h4>Advanced</h4>
-
<dl>
-<dt>Command line key generation</dt>
-<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>
-
<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 much more
+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="http://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 -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-2b" class="step">
-<div class="main">
-
-<h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
+<div class="sidebar">
+<p><img
+src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step2b-04-upload-and-certificate.png"
+alt="Step 2.A: Send to server and generate a certificate" /></p>
-<p>In your email program's menu, select Enigmail → Key Management.</p>
+</div><!-- /.sidebar -->
+<div class="main">
-<p>Right click on your key and select Upload Public Keys to Keyserver. You
-don't have to use the default keyserver. If, after research, you would like
-to change to a different default keyserver, you can change that setting
-manually in the Enigmail preferences.</p>
+<h3><em>Step 2.b</em> Some important steps following creation</h3>
-<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
+<h6>Upload your key to a keyserver</h6>
+<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 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>
+<p># Copy your keyID <text style="color:#2f5faa; font-family: monospace;">gnupg --list-key [your@email]</text> will list your public ("pub") key information, including your keyID, which is a unique list of numbers and letters. Copy this keyID, so you can use it in the following command.</p>
+<p># Upload your key to a server: <text style="color:#2f5faa; font-family: monospace;">gpg --send-key [keyID]</text></p>
+
+<br />
+
+<h6>Generate a certificate</h6>
+<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 (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>.</p>
+<p># Copy your keyID <text style="color:#2f5faa; font-family: monospace;">gnupg --list-key [your@email]</text> will list your public ("pub") key information, including your keyID, which is a unique list of numbers and letters. Copy this keyID, so you can use it in the following command.</p>
+<p># Upload your key to a server: <text style="color:#2f5faa; font-family: monospace;">gpg --output-revoke.asc [keyID]</text></p>
+<p># It will prompt you to give a reason for revocation, we recommend to use <text style="color:#2f5faa; font-family: monospace;">1 "key has been compromised"</text></p>
+<p># You don't have to fill in a reason, but you can, then press enter for an empty line, and comfirm your selection.</p>
+
+<br />
+
+<h6>Export your key to a file</h6>
+<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>
+
+<text style="color:#2f5faa; font-family: monospace;">
+<p>$ gpg --export-secret-keys -a keyid > my_secret_key.asc</p>
+<p>$ gpg --export -a keyid > my_public_key.asc</p>
+</text>
+
+<br />
<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">
<h4>Troubleshooting</h4>
<dl>
-<dt>The progress bar never finishes</dt>
-<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>
+<dt>My key is doesn't seem to be working or i get a "permission denied".</dt>
+<dd>Like everything other file or folder, gpg keys are subject to permissions. If these are not set correctly, your system may not be accepting your keys, you can follow the next steps to check, and update to the right permissions.</p>
-<dt>My key doesn't appear in the list</dt>
-<dd>Try checking "Display All Keys by Default."</dd>
-
-<dt>More documentation</dt>
-<dd>If you're having trouble with our
-instructions or just want to learn more, check out <a
-href="https://www.enigmail.net/documentation/Key_Management#Distributing_your_public_key">
-Enigmail's documentation</a>.</dd>
+# Check your permissions: <text style="color:#2f5faa; font-family: monospace;">ls -l ~/.gnupg/*</text></p>
+# Set permissions to read, write, execute for only yourself, no others. This is the recommended permission for your folder, you can use the code <text style="color:#2f5faa">
+chmod 700 ~/.gnupg</text>.</p>
+# Set permissions to read, write for only yourself, no others. This is the recommended permission for the keys inside your folder, you can use the code: <text style="color:#2f5faa; font-family: monospace;">chmod 600 ~/.gnupg/*</text>.</p>
+<p class="notes"><p>If you have (for any reason) created your own folders inside ~/.gnupg, you must also additionally apply execute permissions to that folder. Folders require execution privileges to be opened. For more information on permissions, you can check out <a href="https://helpdeskgeek.com/linux-tips/understanding-linux-permissions-chmod-usage/">this detailed information guide</a>.</p>
+</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
<h4>Advanced</h4>
<dl>
-<dt>Uploading a key from the command line</dt>
-<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
+<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>Use the following commands transfer your keys. To avoid getting your key compromised, store it in a safe place, and make sure that if it is transferred, it is done so in a trusted way. Importing and exporting a key can be done with the following commands:</p>
+
+<text style="color:#2f5faa; font-family: monospace;">
+$ gpg --export-secret-keys -a keyid > my_private_key.asc</p>
+$ gpg --export -a keyid > my_public_key.asc</p>
+</text>
+
+<text style="color:#2f5faa; font-family: monospace;">
+$ gpg --import my_private_key.asc</p>
+$ gpg --import my_public_key.asc</p>
+</text>
+
+Ensure that the Key ID printed is the correct one, and if so, then go ahead and add ultimate trust for it:</p>
+<text style="color:#2f5faa; font-family: monospace;">
+$ gpg --edit-key [your@email]</p>
+</text>
+
+Because this is your key, you should choose <text style="color:#2f5faa; font-family: monospace;">ultimate</text>. You shouldn't trust anyone else's key ultimately.
+</dd>
</dl>
</div><!-- /.troubleshooting -->
<div id="terminology" class="step">
<div class="main">
-<h3>GnuPG, OpenPGP, what?</h3>
+<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. Enigmail is a plug-in program
-for your email program that provides an interface for GnuPG.</p>
+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 #section2 -->
-<!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
-<section
class="row" id="section3"><div>
+<!-- ~~~~~~~~~ Section 3: Set up email encryption ~~~~~~~~~ -->
+<section
id="section3" class="row"><div>
<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">
-<h2><em>#3</em> Try it out!</h2>
+<h2><em>#3</em> Set up email encryption</h2>
+<p class="notes"><p>Icedove and Thunderbird email programs have PGP functionality integrated, which makes it pretty easy to work with. We'll take you through the steps of integrating and using your key in these email clients.</p>
+
+</div><!-- End .section-intro -->
+
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-3a" class="step">
+<div class="sidebar">
+
+<p><img src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step3a-open-key-manager.png"
+alt="Step 3.A: Thunderbird Menu" /></p>
+<p><img src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step3a-import-from-file.png"
+alt="Step 3.A: Import From File" /></p>
+<p><img src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step3a-select-file.png"
+alt="Step 3.A: Select File" /></p>
+<p><img src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step3a-success.png"
+alt="Step 3.A: Success" /></p>
+</div><!-- /.sidebar -->
+<div class="main">
+
+<h3><em>Step 3.a</em> Set up your email with encryption</h3>
+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># Open your email client and use "Tools" → <text style="color:#2f5faa;">OpenPGP Manager</p></text></p>
+<p># Under "File" → <text style="color:#2f5faa;">Import Secret Key(s) From File</text></p>
+<p># Select the file you saved under the name [my_secret_key.asc] in step <a href="#step-3b">step 3.b</a> when you exported your key</p>
+<p># Unlock with your passphrase</p>
+<p># You will receive a "OpenPGP keys successfully imported" window to confirm success</p>
+<p># Go to "Edit" (in Icedove) or "Tools" (in Thunderbird) → "Account settings" → "End-To-End Encryption", and make sure your key is imported and select <text style="color:#2f5faa;">Treat this key as a Personal Key</p></text>.
+</div><!-- End .main -->
+
+<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+<div class="sidebar">
+
+<p><img src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step3a-troubleshoot.png"
+alt="Step 3.A: Troubleshoot" /></p>
+</div><!-- /.sidebar -->
+
+<div class="main">
+<div class="troubleshooting">
+<h4>Troubleshooting</h4>
+<dl>
+<dt>I'm not sure the import worked correctly</dt>
+<dd>
+Under "Edit" (in Icedove) or "Tools" (in Thunderbird) look for "Account settings" → "End-To-End Encryption" you can see if your personal key associated with this email is found. If it is not, you can try again via the <text style="color:#2f5faa;">Add key</text> option. Make sure you have the correct, active, secret key file.
+</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><img style="float:right; width:250px; margin-bottom:20px;" src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" alt="Illustration of a person in a house with a cat connected to a server"/></p>
<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>
</div><!-- End .section-intro -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-3a" class="step">
+<div id="step-4a" class="step">
<div class="sidebar">
<p><img
-src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png"
-alt="Try it out." /></p>
+src="//static.fsf.org/nosvn/enc-dev1/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 3.a</em> Send Edward your public key</h3>
+<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 Enigmail → Key
-Management. You should see your key in the list that pops up. Right click
+with real people. In your email program's menu, go to "Tools" → "OpenPGP Key
+Manager". 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>
+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>The lock icon in the top left should be yellow, meaning encryption is
-turned on. We want this first special message to be unencrypted, so
-click the icon once to turn it off. The lock should become grey, with a
-blue dot on it (to alert you that the setting has been changed from the
-default). Once encryption is off, hit Send.</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 drowpdown menu "Security" and select <text style="color:#2f5faa">Do Not Encrypt</text>. 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="#section5">Use it Well</a> section of this guide. Once he's responded,
+href="#section6">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>
-<p>When you open Edward's reply, GnuPG may prompt you for your password
+<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-3a .step -->
+</div><!-- End #step-4a .step -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-3b" class="step">
-<div class="main">
-
-<h3><em>Step 3.b</em> Send a test encrypted email</h3>
+<div id="step-4b" class="step">
+<div class="sidebar">
-<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><img
+src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step4b-option1-verify-key.png"
+alt="Step 4.B Option 1. Verify key" /></p>
+<p><img
+src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step4b-option2-import-key.png"
+alt="Step 4.B Option 2. Import key" /></p>
+</div><!-- /.sidebar -->
-<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>
+<div class="main">
-<p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll
-get to this in a moment.</p>
+<h3><em>Step 4.b</em> Send a test encrypted email</h3>
+<h6>Get Edward's key</h6>
+<p>To encrypt an email to Edward, you need his public key, so now you'll have
+to download it from a keyserver. You can do this in two different ways:</p>
+<p>Option 1. In the email answer you received from Edward as a response to your first email, Edward's public key was included. On the right of the email, just above the writing area, you will find an "OpenPGP" button that has a lock and a little wheel next to it. Click that, and select <text style="color:#2f5faa">Discover</text> next to the text: "This message was sent with a key that you don't have yet." A popup with Edward's key details will follow.
-<p>Click Send. Enigmail will pop up a window that says "Recipients not valid,
-not trusted or not found."</p>
+<p>Option 2. Open your OpenPGP manager and under "Keyserver" choose <text style="color:#2f5faa">Discover Keys Online</text>. Here, fill in Edward's email address, and import Edward's key.
-<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>
+<p>The option <text style="color:#2f5faa">Accepted (unverified)</text> will add this key to your key manager, and now it can be used to send encrypted emails and to verify digital signatures from Edward.</p>
-<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>
+<p class="notes">Edward has many different emails associated with its key, 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
his private key, so no one except him can decrypt it.</p>
+<br />
+<h6>Send Edward an encrpyted email</h6>
+
+<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 drowpdown menu "Security" and select <text style="color:#2f5faa">Require Encryption</text>. Once encryption is on, hit Send.</p>
+
+<br />
+
<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">
<h4>Troubleshooting</h4>
<dl>
-<dt>Enigmail can't find Edward's key</dt>
+<dt>"Recipients not valid, not trusted or not found"</dt>
+<dd>You may be trying to send an ecrypted email to someone when you do not have their public key yet. Make sure you follow the steps above to import the key to your key manager. Open OpenPGP Key Manager to make sure the recipient is listed there.</dd>
+
+<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, if you go to the "key properties" of this key by right clicking on the key in the OpenPGP Key Manager, you can select the option <text style="color:#2f5faa">Yes, but I have not verified that this is the correct key.</text> in the "Acceptance" option at the bottom of this window. Resend the email.</dd>
+
+<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, repeat
the process, choosing a different keyserver when it asks you to pick one.</dd>
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>More resources</dt>
-<dd>If you're still having trouble with our
-instructions or just want to learn more, check out <a
-href="https://www.enigmail.net/documentation/Signature_and_Encryption#Encrypting_a_message">
-Enigmail's wiki</a>.</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
</div><!-- /.troubleshooting -->
</div><!-- End .main -->
-</div><!-- End #step-3b .step -->
+</div><!-- End #step-4b .step -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-headers_unencrypted" class="step">
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,
+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
</div><!-- End #step-headers_unencrypted .step-->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-3c" class="step">
+<div id="step-4c" class="step">
+<div class="sidebar">
+
+<p><img
+src="//static.fsf.org/nosvn/enc-dev1/img/en/screenshots/step4c-Edward-response.png"
+alt="Step 4.C Edward's response" /></p>
+
+</div><!-- /.sidebar -->
+
<div class="main">
-<h3><em>Step 3.c</em> Receive a response</h3>
+<h3><em>Step 4.c</em> Receive a response</h3>
<p>When Edward receives your email, he will use his 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="#section5">Use it Well</a> section of this guide.</p>
+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 decypted. Your email client will automatically decrypt Edward's message.</p>
+
+<p class="notes">The OpenPGP button in the email will show a little green v over the lock symbol to show the message is encypted, and a little orange warning sign which means that you have accepted the key, but not verified it. When you have not yet accepted the key, you will see a little question mark there. Clicking the prompts in this button will lead you to key properties as well.</p>
</div><!-- End .main -->
-</div><!-- End #step-3c .step -->
+</div><!-- End #step-4c .step -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-3d" class="step">
+<div id="step-4d" class="step">
<div class="main">
-<h3><em>Step 3.d</em> Send a test signed email</h3>
+<h3><em>Step 4.d</em> Send a test signed 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
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>With the lock and pencil icons, you can choose whether each message will
-be encrypted, signed, both, or neither.</p>
+<p>In "Account Settings" → "End-To-End-Encryption" you can opt to <text style="color:#2f5faa">add digital signature by default</text>.</p>
-</div>
-</div>
+</div><!-- End .main -->
+</div><!-- End #step-4d .step -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-3e" class="step">
+<div id="step-4e" class="step">
<div class="main">
-<h3><em>Step 3.e</em> Receive a response</h3>
+<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
<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>
+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, Enigmail will
+<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>
-<p>Notice the bar that Enigmail shows you above the message, with
-information about the status of Edward's key.</p>
-
</div><!-- End .main -->
-</div><!-- End #step-3e .step -->
+</div><!-- End #step-4e .step -->
</div></section>
-<!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
-<section class="row" id="section
4"><div>
+<!-- ~~~~~~~~~ Section 5: Learn the Web of Trust ~~~~~~~~~ -->
+<section class="row" id="section
5"><div>
<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">
-<h2><em>#4</em> Learn the Web of Trust</h2>
+<h2><em>#5</em> Learn the Web of Trust</h2>
+<p><img style="float:right; width:250px; margin-bottom:20px;" src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Illustration of keys all interconnected with a web of lines"/></p>
<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
</div><!-- End .section-intro -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-4a" class="step">
+<div id="step-5a" class="step">
<div class="sidebar">
<p><img
-src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png"
-alt="Section 4: Web of Trust" /></p>
+src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step5a-key-properties.png"
+alt="Section 5: trusting a key" /></p>
</div><!-- /.sidebar -->
<div class="main">
-<h3><em>Step 4.a</em> Sign a key</h3>
-
-<p>In your email program's menu, go to Enigmail → Key Management.</p>
+<h3><em>Step 5.a</em> Sign a key</h3>
-<p>Right click on Edward's public key and select Sign Key from the context
-menu.</p>
+<p>In your email program's menu, go to OpenPGP Key Manager and select <text style="color:#2f5faa">Key properties</text> by right clicking on Edward's key.</p>
-<p>In the window that pops up, select "I will not answer" and click ok.</p>
-
-<p>Now you should be back at the Key Management menu. Select Keyserver →
-Upload Public Keys and hit ok.</p>
+<p>Under "Your Acceptance", you can select <text style="color:#2f5faa">Yes, I've verified in person this key has the correct fingerprint"</text></p>
<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>
+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">
</div>End #pgp-pathfinder -->
</div><!-- End .main -->
-</div><!-- End #step-4a .step -->
+</div><!-- End #step-5a .step -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-identify_keys" class="step">
<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 → Key
+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
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?"</p>
+sure the name on the ID matches the name on the public key.</p>
<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">
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>
-
-<dt>Set ownertrust</dt>
-<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>
</dl>
</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #check-ids-before-signing .step-->
-</div></section><!-- End #section4 -->
+</div></section><!-- End #section5 -->
-<!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
-<section id="section
5" class="row"><div>
+<!-- ~~~~~~~~~ Section 6: Use it well ~~~~~~~~~ -->
+<section id="section
6" class="row"><div>
<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">
-<h2><em>#5</em> Use it well</h2>
+<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
</div><!-- End .section-intro -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-5a" class="step">
+<div id="step-6a" class="step">
<div class="sidebar">
<p><img
src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png"
-alt="Section 5: Use it Well (1)" /></p>
+alt="Section 6: Use it Well (1)" /></p>
</div><!-- /.sidebar -->
<div class="main">
(the text kind, not the cryptographic kind).</p>
</div><!-- End .main -->
-</div><!-- End #step-5a .step -->
+</div><!-- End #step-6a .step -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-5b" class="step">
+<div id="step-6b" class="step">
<div class="sidebar">
<p><img
src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png"
-alt="Section 5: Use it Well (2)" /></p>
+alt="Section 6: Use it Well (2)" /></p>
</div><!-- /.sidebar -->
<div class="main">
<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>
+green v a at the top "OpenPGP" button.</p>
-<p><b>When using GnuPG, make a habit of glancing at that bar. The program
+<p><b>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.</b></p>
</div><!-- End .main -->
-</div><!-- End #step-5b .step -->
+</div><!-- End #step-6b .step -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-5c" class="step">
+<div id="step-6c" class="step">
<div class="main">
<h3>Copy your revocation certificate to somewhere safe</h3>
file to let people know that you are no longer using that keypair.</p>
</div><!-- End .main -->
-</div><!-- End #step-5c .step -->
+</div><!-- End #step-6c .step -->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
<div id="step-lost_key" class="step">
</div><!-- End .main -->
</div><!-- End #step-lost_key .step-->
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<!---<div id="transfer-key" class="step">
-<div class="main">
-
-<h3>Transferring you key</h3>
-
-<p>You can use Enigmail's <a
-href="https://www.enigmail.net/documentation/Key_Management">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>
-
-</div>--><!-- End .main
-</div> End #transfer-key .step-->
-
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
<div id="webmail-and-GnuPG" class="step">
<div class="main">
</div><!-- End #webmail-and-GnuPG .step-->
<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
-<div id="step-5d" class="step">
+<div id="step-6d" class="step">
<div class="main">
<h3>Make your public key part of your online identity</h3>
email address without a public key fingerprint.</p>
</div>--><!-- End .main
-</div> End #step-5d .step-->
-</div></section><!-- End #section5 -->
+</div> End #step-6d .step-->
+</div></section><!-- End #section6 -->
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
+<!-- ~~~~~~~~~ Section 7: Next steps ~~~~~~~~~ -->
<section class="row" id="section6">
<div id="step-click_here" class="step">
<div class="main">
</div><!-- End .main -->
</div><!-- End #step-click_here .step-->
-</section><!-- End #section6 -->
+</section><!-- End #section7 -->
<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
<!-- When un-commenting this section go to main.css and search
alt="Free Software Foundation"
src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" /></a></h4>
-<p>Copyright © 20
14-2016 <a
+<p>Copyright © 20
21 <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
projects / enc-live.git / commitdiff