From 89a0794d17755137192eeb881bb59c240a63fe09 Mon Sep 17 00:00:00 2001 From: zoe1 Date: Wed, 14 Jul 2021 23:17:36 +0200 Subject: [PATCH] fixed an error --- en/index.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/en/index.html b/en/index.html index 7b3b2c7..15d912b 100644 --- a/en/index.html +++ b/en/index.html @@ -825,8 +825,8 @@ takes a few hours for them to match each other when a new key is uploaded.

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-secret-keys -a [keyid] > my_secret_key.asc
+$ gpg --export -a [keyid] > my_public_key.asc


@@ -835,7 +835,7 @@ $ gpg --export -a keyid > my_public_key.asc

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 --output revoke.asc [keyID]

+

# Generate a revocation certificate: gpg --gen-revoke --output revoke.asc [keyID] [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.

-- 2.25.1