Home Explore Help
Sign In
mirrors
/
borg
mirror of https://github.com/borgbackup/borg
2
0
Fork 0
Files Issues 0 Wiki
Tree: 99be106bc8
Branches Tags
borg
/
docs
/
support.rst

support.rst 2.0 KB
History Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354 
  1. .. _support:
    2. 

  2. 

  3. Support
    4. 

  4. =======
    5. 

  5. 

  6. Support and Services
    7. 

  7. --------------------
    8. 

  8. 

  9. Please see https://www.borgbackup.org/ for free and paid support and service options.
    10. 

  10. 

  11. 

  12. .. _security-contact:
    13. 

  13. 

  14. Security
    15. 

  15. --------
    16. 

  16. 

  17. In case you discover a security issue, please use this contact for reporting it privately
    18. 

  18. and please, if possible, use encrypted E-Mail:
    19. 

  19. 

  20. Thomas Waldmann <tw@waldmann-edv.de>
    21. 

  21. 

  22. GPG Key Fingerprint: 6D5B EF9A DD20 7580 5747  B70F 9F88 FB52 FAF7 B393
    23. 

  23. 

  24. The public key can be fetched from any GPG keyserver, but be careful: you must
    25. 

  25. use the **full fingerprint** to check that you got the correct key.
    26. 

  26. 

  27. Verifying signed releases
    28. 

  28. -------------------------
    29. 

  29. 

  30. `Releases <https://github.com/borgbackup/borg/releases>`_ are signed with the same GPG key and a .asc file is provided for each binary.
    31. 

  31. 

  32. 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::
    33. 

  33. 

  34.       gpg --recv-keys "6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393"
    35. 

  35. 

  36. If GPG successfully imported the key, the output should be (among other things): 'Total number processed: 1'.
    37. 

  37. 

  38. To verify for example the signature of the borg-linux64 binary::
    39. 

  39. 

  40.       gpg --verify borg-linux64.asc
    41. 

  41. 

  42. GPG outputs if it finds a good signature. The output should look similar to this::
    43. 

  43. 

  44.       gpg: Signature made Sat 30 Dec 2017 01:07:36 PM CET using RSA key ID 51F78E01
    45. 

  45.       gpg: Good signature from "Thomas Waldmann <email>"
    46. 

  46.       gpg: aka "Thomas Waldmann <email>"
    47. 

  47.       gpg: aka "Thomas Waldmann <email>"
    48. 

  48.       gpg: aka "Thomas Waldmann <email>"
    49. 

  49.       gpg: WARNING: This key is not certified with a trusted signature!
    50. 

  50.       gpg: There is no indication that the signature belongs to the owner.
    51. 

  51.       Primary key fingerprint: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
    52. 

  52.       Subkey fingerprint: 2F81 AFFB AB04 E11F E8EE 65D4 243A CFA9 51F7 8E01
    53. 

  53. 

  54. 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.
    55.