From e4266c8121fa4cbc276378ac66ccf85b168d240b Mon Sep 17 00:00:00 2001 From: =?utf8?q?Th=C3=A9r=C3=A8se=20Godefroy?= Date: Tue, 20 Jul 2021 22:05:35 +0200 Subject: [PATCH] en: synchronize with enc-live. --- en/index.html | 419 +------------------------------------------------- 1 file changed, 3 insertions(+), 416 deletions(-) diff --git a/en/index.html b/en/index.html index af5fd35b..f61a31ee 100644 --- a/en/index.html +++ b/en/index.html @@ -15,424 +15,11 @@ self-defense in 40 minutes with GnuPG." /> href="../static/img/favicon.ico" /> - + - - - - -

@@ -852,9 +439,9 @@ $ gpg --export -a [keyid] > my_public_key.asc

Like every 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/*

-# Set permissions to read, write, execute for only yourself, no others. This is the recommended permission for your folder.
+# Set permissions to read, write, execute for only yourself, no others. These are the recommended permissions for your folder.
You can use the code chmod 700 ~/.gnupg

-# Set permissions to read and write for yourself only, no others. This is the recommended permission for the keys inside your folder.
+# Set permissions to read and write for yourself only, no others. These are the recommended permissions for the keys inside your folder.
You can use the code: chmod 600 ~/.gnupg/*

If you have (for any reason) created your own folders inside ~/.gnupg, you must also additionally apply execute permissions to that folder. Folders require execution privileges to be opened. For more information on permissions, you can check out this detailed information guide.

-- 2.25.1

Move freedom forward with a donation to the FSF!