mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2025-01-23 15:58:55 +00:00
Code Issues Releases Wiki Activity

Improve formatting of GPG output in documentation

Browse source
This commit is contained in:
Josh Holland 2018-03-05 13:21:20 +00:00
parent b862c15691
commit 9f2f4132ec
No known key found for this signature in database
GPG key ID: 638D16FE887043C2
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/support.rst
View file

@ -29,17 +29,17 @@ Verifying signed releases
`Releases <https://github.com/borgbackup/borg/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 <email>"