From 9c973564197d6aacbe890b66f1abd658a423b9d5 Mon Sep 17 00:00:00 2001 From: zoe1 Date: Fri, 4 Feb 2022 23:19:27 +0100 Subject: [PATCH] relation keyservers change updated --- en/index.html | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/en/index.html b/en/index.html index 815a9fd..b21f0dc 100644 --- a/en/index.html +++ b/en/index.html @@ -408,9 +408,8 @@ alt="Step 2.B: Send to server and generate a certificate" />

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.

+that you can select from the menu when you upload, but they are mostly all copies +of each other. Any server will work, but it's good to remember which one you uploaded your key to originally. Also keep in mind, sometimes takes a few hours for them to match each other when a new key is uploaded.

# 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]

-- 2.25.1