From 99d3c5e17171435874a01bdbc85ad0841b65e910 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Th=C3=A9r=C3=A8se=20Godefroy?= <godef.th@free.fr> Date: Wed, 4 Aug 2021 14:11:21 +0200 Subject: [PATCH] en/index: one more fix; revert unnecessary change. --- en/index.html | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/en/index.html b/en/index.html index 9b8c416e..0d8f59a9 100644 --- a/en/index.html +++ b/en/index.html @@ -409,10 +409,10 @@ takes a few hours for them to match each other when a new key is uploaded.</p> <h4>Export your key to a file</h4> <p>Use the following command to export your secret key so you can import it into your email client at the next <a href="#section3">step</a>. To avoid getting your key compromised, store this in a safe place, and make sure that if it is transferred, it is done so in a trusted way. Exporting your keys can be done with the following commands:</p> -<p> -<code>$ gpg --export-secret-keys -a [keyID] > my_secret_key.asc</code> -<code>$ gpg --export -a [keyID] > my_public_key.asc</code> -</p> +<p><code> +$ gpg --export-secret-keys -a [keyID] > my_secret_key.asc<br/> +$ gpg --export -a [keyID] > my_public_key.asc +</code></p> <h4>Generate a revocation certificate</h4> <p>Just in case you lose your key, or it gets compromised, you want to generate a certificate and choose to save it in a safe place on your computer for now (please refer to <a href="#step-6c"> step 6.C</a> for how to best store your revocation cerficate safely). This step is essential for your email self-defense, as you'll learn more about in <a href="#section5">Section 5</a>.</p> @@ -466,12 +466,12 @@ your key</a> as a file on your computer.</dd> <dd> <p>Use the following commands to transfer your keys. To avoid getting your key compromised, store it in a safe place, and make sure that if it is transferred, it is done so in a trusted way. Importing and exporting a key can be done with the following commands:</p> -<p> -<code>$ gpg --export-secret-keys -a [keyID] > my_private_key.asc</code> -<code>$ gpg --export -a [keyID] > my_public_key.asc</code> -<code>$ gpg --import my_private_key.asc</code> -<code>$ gpg --import my_public_key.asc</code> -</p> +<p><code> +$ gpg --export-secret-keys -a [keyID] > my_private_key.asc<br /> +$ gpg --export -a [keyID] > my_public_key.asc<br /> +$ gpg --import my_private_key.asc<br /> +$ gpg --import my_public_key.asc +</code></p> <p>Ensure that the keyID printed is the correct one, and if so, then go ahead and add ultimate trust for it:</p> @@ -479,7 +479,7 @@ your key</a> as a file on your computer.</dd> $ gpg --edit-key [your@email] </code></p> -<p>Because this is your key, you should choose <code>ultimate</code>. You shouldn't trust anyone else's key ultimately.</p> +<p>Because this is your key, you should choose <code>ultimate</code>. You shouldn't trust anyone else's key ultimately.</p> <p class="notes"> Refer to <a href="#step-2b">Troubleshooting in Step 2.B</a> for more information on permissions. When transferring keys, your permissions may get mixed, and errors may be prompted. These are easily avoided when your folders and files have the right permissions</p> </dd> -- 2.25.1