@@ -766,16 +781,6 @@ takes a few hours for them to match each other when a new key is uploaded.
-
Generate a 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 (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 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.
-
# Upload your key to a server: gpg --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.
-
-
-
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:
@@ -786,13 +791,23 @@ takes a few hours for them to match each other when a new key is uploaded.
+
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.
+
# Upload your key to a server: gpg --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.
+
+
+
Troubleshooting
-- My key is doesn't seem to be working or i get a "permission denied".
+- My key is doesn't seem to be working or I get a "permission denied".
- 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.
# Check your permissions: ls -l ~/.gnupg/*
@@ -843,26 +858,14 @@ $ gpg --edit-key [your@email]
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 have are easily avoided when your folders and files have the right permissions
-
-
-# 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