From e3dfeab2a4c8d31292cda4e2ee4e4bf83417c4bb Mon Sep 17 00:00:00 2001 From: revsuine Date: Mon, 16 Dec 2024 20:26:45 +0000 Subject: [PATCH] content/blog/pgp_encrypting_all_incoming_emails.md: remove spaces between hostname and $ as i think it makes it easier to read --- content/blog/pgp_encrypting_all_incoming_emails.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/blog/pgp_encrypting_all_incoming_emails.md b/content/blog/pgp_encrypting_all_incoming_emails.md index d7bdeb9..90f8e57 100644 --- a/content/blog/pgp_encrypting_all_incoming_emails.md +++ b/content/blog/pgp_encrypting_all_incoming_emails.md @@ -135,10 +135,10 @@ You are now done from the admin side of things. In order for gpgmymail (the script linked above) to have the user's public PGP key, they need to import it to their system GnuPG keyring. If they have shell access, - user@localhost $ gpg --export --armor user@revsuine.xyz > public.asc - user@localhost $ scp public.asc user@revsuine.xyz:~/public.asc - user@localhost $ ssh user@revsuine.xyz - user@revsuine.xyz $ gpg --import ~/public.asc + user@localhost$ gpg --export --armor user@revsuine.xyz > public.asc + user@localhost$ scp public.asc user@revsuine.xyz:~/public.asc + user@localhost$ ssh user@revsuine.xyz + user@revsuine.xyz$ gpg --import ~/public.asc Or you could copy and paste the ASCII armored public key into an SSH shell, etc. @@ -156,7 +156,7 @@ as their user (e.g. with `doas -u`). You also need to mark the public key as trusted so that GPG doesn't refuse to encrypt data with the key: - user@revsuine.xyz $ gpg --edit-key user@revsuine.xyz + user@revsuine.xyz$ gpg --edit-key user@revsuine.xyz Then enter `trust`, select `5`, enter `y`, then enter `save`: