From bb432ab51d7c8e1af65c7a470c6798e9cd70c590 Mon Sep 17 00:00:00 2001 From: Adam Leibson Date: Tue, 18 Aug 2015 15:06:43 -0400 Subject: [PATCH] commit --- en/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/index.html b/en/index.html index f0482f2..6200973 100644 --- a/en/index.html +++ b/en/index.html @@ -236,7 +236,7 @@
Command line key generation
-
If you prefer using the command line for a higher degree of control, you can follow the documentation from The GNU Privacy Handbook. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than the algorithms recommended in the old previously mentioned documentation.
+
If you prefer using the command line for a higher degree of control, you can follow the documentation from The GNU Privacy Handbook. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than the algorithms recommended documentation. Also make sure your key is at least 2048 bits, or 4096 if you really want to be secure.
Advanced key pairs
When GnuPG creates a new keypair, it compartmentalizes the encryption function from the signing function through subkeys. If you use subkeys carefully, you can keep your GnuPG identity much more secure and recover from a compromised key much more quickly. Alex Cabal and the Debian wiki provide good guides for setting up a secure subkey configuration.
-- 2.25.1