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>
+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://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
Mac OS). Learn more about free software at <a
+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,
</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #step1-a .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 ~~~~~~~~~ -->
<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.
+<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; 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; font-family: monospace;">gpg --full-generate-key</text> to start the process.</p>
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>
+<dd>That's okay. It's important to think about your passphrase, when you're ready, just follow the steps to create your key again.</dd>
<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>
+Use the following command to see all keys <text style="color:#2f5faa; font-family: monospace;">gnupg --list-keys</text>. Yours should be listed in there, and later, so will Edward's (<a href="#section3">section 3</a>). If you want to see only your key, you can use <text style="color:#2f5faa; font-family: monospace;">gnupg --list-key [your@email]</text>
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>
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>
+recommends. Also make sure your key is at least 4096 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
<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>
+alt="Step 2.B: Send to server and generate a certificate" /></p>
</div><!-- /.sidebar -->
<div class="main">
<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>
<br />
+<h6>Generate a revocation 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 for now (please refer to <a href="#step-6c"> step 6.C for how to best store your revocation cerficate safely). This step is essential for your email self-defense, as you'll learn more about in <a href="#section5">Section
+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 />
+
<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">
<h4>Troubleshooting</h4>
<dl>
-<dt>My key is doesn't seem to be working or i get a "permission denied".</dt>
+<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>
# Check your permissions: <text style="color:#2f5faa; font-family: monospace;">ls -l ~/.gnupg/*</text></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.
+
+<p class="notes"> Refer to <a href="#step-2b">troubleshoot in step 2.B</a> for more information on permissions. When transferring keys, your permissions may get mixed, and errors may be prompted. These have are easily avoided when your folders and files have the right permissions</p>
</dd>
</dl>
</div><!-- /.troubleshooting -->
</div><!-- End .main -->
</div><!-- End #step-2b .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 #section2 -->
<!-- ~~~~~~~~~ Section 3: Set up email encryption ~~~~~~~~~ -->
<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>.
+<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</text>.</p>
</div><!-- End .main -->
<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" → "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, but in the attachment you will find your public keyfile.</p>
+on your key and select <text style="color:#2f5faa;">Send Public Keys by Email</text>. This will create a new draft message, as if you had just hit the "Write" button, but in the attachment you will find your public keyfile.</p>
<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 drowpdown menu "Security" and select <text style="color:#2f5faa">Do Not Encrypt</text>. 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 dropdown 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
<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
+<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>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 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>
+its private key, so no one except Edward can decrypt it.</p>
<br />
<h6>Send Edward an encrpyted email</h6>
<dl>
<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>
+<dd>You may be trying to send an encrypted email to someone when you do not have their public key yet. Make sure you follow the steps above to import the key to your key manager. Open OpenPGP Key Manager to make sure the recipient is listed there.</dd>
<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>
<h3><em>Step 4.c</em> Receive a response</h3>
-<p>When Edward receives your email, he will use his private key to decrypt
+<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
<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>
+<p class="notes">The OpenPGP button in the email will show a little green checkmark over the lock symbol to show the message is encypted, and a little orange warning sign which means that you have accepted the key, but not verified it. When you have not yet accepted the key, you will see a little question mark there. Clicking the prompts in this button will lead you to key properties as well.</p>
</div><!-- End .main -->
</div><!-- End #step-4c .step -->
<div id="step-4d" class="step">
<div class="main">
-<h3><em>Step 4.d</em> Send a test signed email</h3>
+<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
<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 his reply to you.</p>
+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
<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 v a at the top "OpenPGP" button.</p>
+green checkmark a at the top "OpenPGP" button.</p>
<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
<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 digital
-storage that you have -- the ideal thing is a flash drive, disk, or hard
-drive stored in a safe place in your home, not on a device you carry with
-you regularly.</p>
+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>
projects / enc-live.git / commitdiff