From 9f2f4132ec5b188ca2019678c6662cabbc0324bb Mon Sep 17 00:00:00 2001 From: Josh Holland Date: Mon, 5 Mar 2018 13:21:20 +0000 Subject: [PATCH] Improve formatting of GPG output in documentation --- docs/support.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/support.rst b/docs/support.rst index d3141ebcd..ce80dacc6 100644 --- a/docs/support.rst +++ b/docs/support.rst @@ -29,17 +29,17 @@ Verifying signed releases `Releases `_ are signed with the same GPG key and a .asc file is provided for each binary. -To verify a signature, the public key needs to be known to GPG. It can be imported into the local keystore from a keyserver with the fingerprint: +To verify a signature, the public key needs to be known to GPG. It can be imported into the local keystore from a keyserver with the fingerprint:: gpg --recv-keys "6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393" If GPG successfully imported the key, the output should be (among other things): 'Total number processed: 1'. -To verify for example the signature of the borg-linux64 binary: +To verify for example the signature of the borg-linux64 binary:: gpg --verify borg-linux64.asc -GPG outputs if it finds a good signature. The output should look similar to this: +GPG outputs if it finds a good signature. The output should look similar to this:: gpg: Signature made Sat 30 Dec 2017 01:07:36 PM CET using RSA key ID 51F78E01 gpg: Good signature from "Thomas Waldmann " @@ -51,4 +51,4 @@ GPG outputs if it finds a good signature. The output should look similar to this Primary key fingerprint: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393 Subkey fingerprint: 2F81 AFFB AB04 E11F E8EE 65D4 243A CFA9 51F7 8E01 -If you want to make absolutely sure that you have the right key, you need to verify it via another channel and assign a trust-level to it. \ No newline at end of file +If you want to make absolutely sure that you have the right key, you need to verify it via another channel and assign a trust-level to it.