Step 1.b Get your terminal ready and install GnuPG
+Step 1.b Install GnuPG
+ +If you are using a GNU/Linux machine, you should already have GnuPG installed, and you can skip to Section 2.
-If you are using a GNU/Linux machine, you should already have GnuPG installed, and you can skip to Step 2.
-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 steps. For the rest of the steps in this guide, the steps are the same for all operating systems.
+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.
MacOS
+macOS
- Use a third-party package manager to install GnuPG -
- 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).
-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 Homebrew and paste it in Terminal. Click "Enter" and wait for it to finalize.
-When it is done, install the program by entering the following code in Terminal:
-brew install gnupg gnupg2. After installation is done, you can follow the steps of the rest of this guide.
+ -
+
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.
+ +# Copy the first command on the home page of Homebrew by clicking on the clipboard icon, and paste it in Terminal. Click "Enter" and wait for the installation to finalize.
+# Then install GnuPG by entering the following code in Terminal:
+
+brew install gnupg gnupg2
- Get GnuPG by downloading GPG4Win -
- GPG4Win is a 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.
- - -To follow the rest of the steps in this guide, you'll use the program called "PowerShell", which is a program you'll see elsewhere referred to as a "terminal." This allows you to operate your computer using the command line.
+GPG4Win 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.
#2 Make your keys
-
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 @@ -274,9 +271,8 @@ look up your public key.
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. You should never share your private key with anyone, under any -circumstances.
+descramble encrypted emails other people send to you. You should never share your private key with anyone, under any +circumstances.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 @@ -287,32 +283,36 @@ discuss this more in the next section.
-
Step 2.a Make a keypair
-Make your keypair
-Open a terminal using ctrl + alt + t (on GNU/linux), or find it in your applications, and use the following code to create your keypair:
-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.
+Make your keypair
-# gpg --full-generate-key to start the process.
-# To answer what kind of key you would like to create, select the default option 1 RSA and RSA.
-# Enter the following keysize: 4096 for a strong key.
-# Choose the expiration date, we suggest 2y (2 years).
+We will use the command line in a terminal to create a keypair using the +GnuPG program.
+ +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 Ctrl + Alt + T +shortcut).
+ +# Enter gpg --full-generate-key to start the process.
# To answer what kind of key you would like to create, select the default option: 1 RSA and RSA.
+# Enter the following keysize: 4096 for a strong key.
# Choose the expiration date; we suggest 2y (2 years).
Follow the prompts to continue setting up with your personal details.
--
Set your passphrase
+Set your passphrase
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 @@ -329,8 +329,6 @@ 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.
--
- GnuPG is not installed
- -GPG is not installed. You can check if this is the case with the command gpg --version. -If GnuPG is not installed, it would bring up the following result on most GNU/Linux operating systems, or something like it: -Command 'gpg' not found, but can be installed with: - sudo apt install gnupg. Follow that command and install the program. +You can check if this is the case with the command
- I took too long to create my passphrase
- 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.
- How can I see my key?
- -Use the following command to see all keys gpg --list-keys. Yours should be listed in there, and later, so will Edward's (section 3). If you want to see only your key, you can use gpg --list-key [your@email]. -You can also use gpg --list-secret-key to see your own private key. +Use the following command to see all keys:
- More resources
- For more information about this process, you can also refer to The GNU Privacy Handbook. 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 bits if you +recommends. Also make sure your key is at least 4096 bits if you want to be secure.
- Don't see a solution to your problem? @@ -390,7 +389,7 @@ provide good guides for setting up a secure subkey configuration.
- My key doesn't seem to be working or I get a "permission denied." -
- 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.
+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.
-# Check your permissions: ls -l ~/.gnupg/*
-# Set permissions to read, write, execute for only yourself, no others. These are the recommended permissions for your folder.
-You can use the code chmod 700 ~/.gnupg
-# Set permissions to read and write for yourself only, no others. These are the recommended permissions for the keys inside your folder.
-You can use the code: chmod 600 ~/.gnupg/*
+# Check your permissions:
+ls -l ~/.gnupg/*# Set permissions to read, write, execute for only yourself, no others. These are the recommended permissions for your folder.
+
+You can use the code:chmod 700 ~/.gnupg# Set permissions to read and write for yourself only, no others. These are the recommended permissions for the keys inside your folder.
-
+You can use the code:chmod 600 ~/.gnupg/*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 this detailed information guide.
+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 this detailed information guide.
- Don't see a solution to your problem?
- Please let us know on the directly export your key as a file on your computer.
- Transferring your keys -
- 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:
+- +
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:
- -$ gpg --export-secret-keys -a keyid > my_private_key.asc
-$ gpg --export -a keyid > my_public_key.asc
-$ gpg --import my_private_key.asc
-$ gpg --import my_public_key.asc
- ++$ gpg --export-secret-keys -a [keyID] > my_private_key.asc
+$ gpg --export -a [keyID] > my_public_key.asc
+$ gpg --import my_private_key.asc
+$ gpg --import my_public_key.asc +Ensure that the keyID printed is the correct one, and if so, then go ahead and add ultimate trust for it:
- + +$ gpg --edit-key [your@email] -
+ -Because this is your key, you should choose ultimate. You shouldn't trust anyone else's key ultimately. +Because this is your key, you should choose
-ultimate. You shouldn't trust anyone else's key ultimately.Refer to troubleshoot in step 2.B 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
+Refer to Troubleshooting in Step 2.B 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
- +
- I'm not sure the import worked correctly
- -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 Add key option. Make sure you have the correct, active, secret key file. +Look for "Account settings" → "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 Add key option. Make sure you have the correct, active, secret key file.
- Don't see a solution to your problem? @@ -563,7 +560,7 @@ page.
- "Recipients not valid, not trusted or not found" -
- 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. +
- 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 OpenPGP Key Manager to make sure the recipient is listed there.
- Unable to send message -
- 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 Yes, but I have not verified that this is the correct key in the "Acceptance" option at the bottom of this window. Resend the email. +
- 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 Yes, but I have not verified that this is the correct key in the "Acceptance" option at the bottom of this window. Resend the email.
- I can't find Edward's key
- Close the pop-ups that have appeared since you clicked Send. Make sure
@@ -717,8 +715,8 @@ independent of the actual email.
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 > Message Body As > Plain -Text.
+to do this in Icedove or Thunderbird, go to "View" → "Message Body As" → Plain +Text.
gpg --version.
+If GnuPG is not installed, it will bring up the following result on most GNU/Linux operating systems, or something like it:
+Command 'gpg' not found, but can be installed with:
+ sudo apt install gnupg. Follow that command and install the program.
gpg --list-keys. Yours should be listed in there, and later, so will Edward's (Section 3).+If you want to see only your key, you can use
gpg --list-key [your@email].+You can also use
gpg --list-secret-key to see your own private key.
Step 2.b Some important steps following creation
-Upload your key to a keyserver
+Upload your key to a keyserver
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.
-# Copy your keyID gnupg --list-key [your@email] 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.
-# Upload your key to a server: gpg --send-key [keyID]
+# Copy your keyID: gpg --list-key [your@email] 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.
# Upload your key to a server:
+gpg --send-key [keyID]
- -
Export your key to a file
+Export your key to a file
Use the following command to export your secret key so you can import it into your email client at the next step. 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:
+
+$ gpg --export-secret-keys -a [keyID] > my_secret_key.asc
+$ gpg --export -a [keyID] > my_public_key.asc
+
-$ gpg --export -a [keyid] > my_public_key.asc
-
- -
- -
Generate a revocation certificate
-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 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 Section 5.
+Generate a revocation certificate
+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 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 Section 5.
-# Copy your keyID gnupg --list-key [your@email] 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.
-# Generate a revocation certificate: gpg --gen-revoke --output revoke.asc [keyID]
-# It will prompt you to give a reason for revocation, we recommend to use 1 "key has been compromised"
-# You don't have to fill in a reason, but you can, then press enter for an empty line, and comfirm your selection.
+# Copy your keyID: gpg --list-key [your@email] 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.
# Generate a revocation certificate: gpg --gen-revoke --output revoke.asc [keyID]
# It will prompt you to give a reason for revocation, we recommend to use 1 = key has been compromised.
+# You don't have to fill in a reason, but you can; then press "Enter" for an empty line, and confirm your selection.
-
-
-
-
Step 3.a Set up your email with encryption
-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. -# Open your email client and use "Tools" → OpenPGP Manager
-# Under "File" → Import Secret Key(s) From File
-# Select the file you saved under the name [my_secret_key.asc] in step step 3.b when you exported your key
+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.
+ +# Open your email client and use "Tools" → OpenPGP Key Manager
+# Under "File" → Import Secret Key(s) From File
+# Select the file you saved under the name [my_secret_key.asc] in Step 2.B when you exported your key
# Unlock with your passphrase
# You will receive a "OpenPGP keys successfully imported" window to confirm success
-# Go to "Edit" (in Icedove) or "Tools" (in Thunderbird) → "Account settings" → "End-To-End Encryption," and make sure your key is imported and select Treat this key as a Personal Key.
+# Go to "Account settings" → "End-To-End Encryption," and make sure your key is imported and select Treat this key as a Personal Key.
#4 Try it out!
-
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.
@@ -572,13 +569,15 @@ steps you'd follow when corresponding with a real, live person. 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. --> + +
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.
+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.Address the message to edward-en@fsf.org. Put at least one word (whatever you want) in the subject and body of the email. Don't send yet.
-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 Do Not Encrypt. Once encryption is off, hit Send.
+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 Do Not Encrypt. Once encryption is off, hit Send.
It may take two or three minutes for Edward to
respond. In the meantime, you might want to skip ahead and check out the
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: 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 Discover 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. 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 Discover 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. Option 2. Open your OpenPGP manager and under "Keyserver" choose Discover Keys Online. Here, fill in Edward's email address, and import Edward's key. Option 2. Open your OpenPGP Key manager, and under "Keyserver" choose Discover Keys Online. Here, fill in Edward's email address, and import Edward's key. The option Accepted (unverified) 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. The option Accepted (unverified) 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. 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. Write a new email in your email program, addressed to edward-en@fsf.org. Make the subject
"Encryption test" or something similar and write something in the body. This time, make sure encryption is turned on by using the dropdown menu "Security" and select Require Encryption. Once encryption is on, hit Send. This time, make sure encryption is turned on by using the dropdown menu "Security" and select Require Encryption. Once encryption is on, hit Send. Edward will send you an encrypted email back saying your email was received and decypted. Your email client will automatically decrypt Edward's message. Edward will send you an encrypted email back saying your email was received and decrypted. Your email client will automatically decrypt Edward's message. 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. In "Account Settings" → "End-To-End-Encryption" you can opt to add digital signature by default. In "Account Settings" → "End-To-End-Encryption" you can opt to add digital signature by default. 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
@@ -828,7 +826,7 @@ that it belongs to them and not someone else. Signing keys and signing messages use the same type of mathematical
operation, but they carry very different implications. It's a good practice
to generally sign your email, but if you casually sign people's keys, you
-may accidently end up vouching for the identity of an imposter. 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
@@ -842,7 +840,7 @@ connected to each other by chains of trust expressed through signatures. In your email program's menu, go to OpenPGP Key Manager and select Key properties by right clicking on Edward's key. In your email program's menu, go to OpenPGP Key Manager and select Key properties by right clicking on Edward's key. Under "Your Acceptance," you can select Yes, I've verified in person this key has the correct fingerprint". Under "Your Acceptance," you can select Yes, I've verified in person this key has the correct fingerprint". 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
@@ -959,7 +957,7 @@ and damage the Web of Trust. When using GnuPG, make a habit of glancing at that button. The program
+ 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.
-
Step 4.b Send a test encrypted email
-Get Edward's key
+
+Get Edward's key
+
-Send Edward an encrypted email
+Send Edward an encrypted email
#5 Learn about the Web of Trust
-
Step 5.a Sign a key
-
