<dd>Your macOS comes with a program called "Terminal" pre-installed, which we'll use to set up your encryption with GnuPG, using the command line. However, the default macOS package manager makes it difficult to install GnuPG and other pieces of free software (like Emacs, GIMP, or Inkscape).</p>
To make things easier, we recommend setting up the third-party package manager "Homebrew" to install GnuPG. Copy the link on the home page of <a href="https://brew.sh/">Homebrew</a> and paste it in Terminal. Click "Enter" and wait for it to finalize.</p>
When it is done, install the program by entering the following code in Terminal:</p>
-<text style="color:#2f5faa; font-family: monospace;">brew install gnupg gnupg2</text>. After installation is done, you can follow the steps of the rest of this guide.</dd>
+<span style="color:#2f5faa; font-family: monospace;">brew install gnupg gnupg2</span>. After installation is done, you can follow the steps of the rest of this guide.</dd>
</dl>
</div><!-- /.troubleshooting -->
<h3><em>Step 2.a</em> Make a keypair</h3>
<h6>Make your keypair</h6>
-<p>Open a terminal using <text style="color:#2f5faa; font-family: monospace;">ctrl + alt + t</text> (on GNU/linux), or find it in your applications, and use the following code to create your keypair:</p>
+<p>Open a terminal using <span style="color:#2f5faa; font-family: monospace;">ctrl + alt + t</span> (on GNU/linux), or find it in your applications, and use the following code to create your keypair:</p>
<p class="notes">We will use the command line in a terminal to create a keypair using the GnuPG program. A terminal should be installed on your GNU/Linux operating system, if you are using a macOS or Windows OS system, use the programs "Terminal" (macOS) or "PowerShell" (Windows) that were also used in section 1.</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># <span style="color:#2f5faa; font-family: monospace;">gpg --full-generate-key</span> to start the process.</p>
+<p># To answer what kind of key you would like to create, select the default option <span style="color:#2f5faa; font-family: monospace;"> 1 RSA and RSA</span>.</p>
+<p># Enter the following keysize: <span style="color:#2f5faa; font-family: monospace;">4096</span> for a strong key.</p>
+<p># Choose the expiration date, we suggest <span style="color:#2f5faa; font-family: monospace;">2y</span> (2 years).</p>
<p>Follow the prompts to continue setting up with your personal details.</p>
<br />
<dl>
<dt>GnuPG is not installed</dt>
<dd>
-GPG is not installed. You can check if this is the case with the command <text style="color:#2f5faa; font-family: monospace;">gpg --version</text>.
+GPG is not installed. You can check if this is the case with the command <span style="color:#2f5faa; font-family: monospace;">gpg --version</span>.
If GnuPG is not installed, it would bring up the following result on most GNU/Linux operating systems, or something like it:
-<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>
+<span style="color:#2f5faa; font-family: monospace;">Command 'gpg' not found, but can be installed with:
+ sudo apt install gnupg</span>. Follow that command and install the program.</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 <text style="color:#2f5faa; font-family: monospace;">gpg --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;">gpg --list-key [your@email]</text>.
-You can also use <text style="color:#2f5faa; font-family: monospace;">gpg --list-secret-key</text> to see your own private key.</dd>
+Use the following command to see all keys <span style="color:#2f5faa; font-family: monospace;">gpg --list-keys</span>. 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 <span style="color:#2f5faa; font-family: monospace;">gpg --list-key [your@email]</span>.
+You can also use <span style="color:#2f5faa; font-family: monospace;">gpg --list-secret-key</span> to see your own private key.</dd>
<dt>More resources</dt>
<dd>For more information about this process, you can also refer to <a
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>
+<p># Copy your keyID <span style="color:#2f5faa; font-family: monospace;">gnupg --list-key [your@email]</span> 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: <span style="color:#2f5faa; font-family: monospace;">gpg --send-key [keyID]</span></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;">
+<span 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>
+</span>
<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</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 <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># Generate a revocation certificate: <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># Copy your keyID <span style="color:#2f5faa; font-family: monospace;">gnupg --list-key [your@email]</span> 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: <span style="color:#2f5faa; font-family: monospace;">gpg --output revoke.asc [keyID]</span></p>
+<p># It will prompt you to give a reason for revocation, we recommend to use <span style="color:#2f5faa; font-family: monospace;">1 "key has been compromised"</span></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 />
<dt>My key doesn't seem to be working or I get a "permission denied."</dt>
<dd>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>
-# 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 and write for yourself only, 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>
+# Check your permissions: <span style="color:#2f5faa; font-family: monospace;">ls -l ~/.gnupg/*</span></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 <span style="color:#2f5faa">
+chmod 700 ~/.gnupg</span>.</p>
+# Set permissions to read and write for yourself only, no others. This is the recommended permission for the keys inside your folder. You can use the code: <span style="color:#2f5faa; font-family: monospace;">chmod 600 ~/.gnupg/*</span>.</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>Transferring your keys</dt>
<dd>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>
-<text style="color:#2f5faa; font-family: monospace;">
+<span 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>
+</span>
-<text style="color:#2f5faa; font-family: monospace;">
+<span style="color:#2f5faa; font-family: monospace;">
$ gpg --import my_private_key.asc</p>
$ gpg --import my_public_key.asc</p>
-</text>
+</span>
Ensure that the keyID 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;">
+<span style="color:#2f5faa; font-family: monospace;">
$ gpg --edit-key [your@email]</p>
-</text>
+</span>
-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.
+Because this is your key, you should choose <span style="color:#2f5faa; font-family: monospace;">ultimate</span>. 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 are easily avoided when your folders and files have the right permissions</p>
</dd>
<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># Open your email client and use "Tools" → <span style="color:#2f5faa;">OpenPGP Manager</p></span></p>
+<p># Under "File" → <span style="color:#2f5faa;">Import Secret Key(s) From File</span></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</text>.</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 <span style="color:#2f5faa;">Treat this key as a Personal Key</span>.</p>
</div><!-- End .main -->
<dl>
<dt>I'm not sure the import worked correctly</dt>
<dd>
-Look for "Account settings" → "End-To-End Encryption" (Under "Edit" (in Icedove) or "Tools" (in Thunderbird)). Here 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.
+Look for "Account settings" → "End-To-End Encryption" (Under "Edit" (in Icedove) or "Tools" (in Thunderbird)). Here you can see if your personal key associated with this email is found. If it is not, you can try again via the <span style="color:#2f5faa;">Add key</span> option. Make sure you have the correct, active, secret key file.
</dd>
<dt class="feedback">Don't see a solution to your problem?</dt>
<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 <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>
+on your key and select <span style="color:#2f5faa;">Send Public Keys by Email</span>. 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 <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 <span style="color:#2f5faa">Do Not Encrypt</span>. 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
<h6>Get Edward's key</h6>
<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 <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><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 <span style="color:#2f5faa">Discover</span> 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><strong>Option 2.</strong> 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><strong>Option 2.</strong> Open your OpenPGP manager and under "Keyserver" choose <span style="color:#2f5faa">Discover Keys Online</span>. Here, fill in Edward's email address, and import Edward's key.
-<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>The option <span style="color:#2f5faa">Accepted (unverified)</span> 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>
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 <text style="color:#2f5faa">Require Encryption</text>. Once encryption is on, hit Send.</p>
+<p>This time, make sure encryption is turned on by using the dropdown menu "Security" and select <span style="color:#2f5faa">Require Encryption</span>. Once encryption is on, hit Send.</p>
<br />
<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." Go to the "key properties" of this key by right clicking on the key in the OpenPGP Key Manager, and 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>
+<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 <span style="color:#2f5faa">Yes, but I have not verified that this is the correct key</span> 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
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" → "End-To-End-Encryption" you can opt to <text style="color:#2f5faa">add digital signature by default</text>.</p>
+<p>In "Account Settings" → "End-To-End-Encryption" you can opt to <span style="color:#2f5faa">add digital signature by default</span>.</p>
</div><!-- End .main -->
</div><!-- End #step-4d .step -->
<h3><em>Step 5.a</em> Sign a key</h3>
-<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 your email program's menu, go to OpenPGP Key Manager and select <span style="color:#2f5faa">Key properties</span> by right clicking on Edward's key.</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>Under "Your Acceptance," you can select <span style="color:#2f5faa">Yes, I've verified in person this key has the correct fingerprint"</span>.</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
projects / enc-live.git / commitdiff