revsuine/revsuine.xyz
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

content/blog/pgp_encrypting_all_incoming_emails.md: remove spaces between hostname and $ as i think it makes it easier to read

Browse source
This commit is contained in:
revsuine 2024-12-16 20:26:45 +00:00
parent acedc16f1a
commit e3dfeab2a4
Signed by: revsuine
GPG key ID: 3F257B68F5BC9339
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
content/blog/pgp_encrypting_all_incoming_emails.md
View file

@ -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`: