-
Notifications
You must be signed in to change notification settings - Fork 77
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d50124e
commit 44c14e9
Showing
1 changed file
with
45 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
# How to verify release binaries signatures | ||
|
||
## Introduction | ||
|
||
Downloading binaries on internet might be dangerous. When you download the binaries of the release of BTCPayServer Vault on our github release page, you only ensure that the uploader had access to our github repository. | ||
|
||
This might be fine, but sometimes you download the same binaries from a different source, or you want additional assurance that those binaries are signed by the developers of the project. (In this case, Nicolas Dorier) | ||
This document explain the process on linux. | ||
|
||
## On linux | ||
|
||
From the release page, download the release binary of your choice, as well as the `SHA256SUMS.asc` file and put those in the same directory. | ||
|
||
```bash | ||
sha256sum --check SHA256SUMS.asc | ||
``` | ||
|
||
If you downloaded archive `BTCPayServerVault-0.0.7.tar.gz` you should see `BTCPayServerVault-0.0.7.tar.gz: OK`. | ||
This make sure that the hashes in `SHA256SUMS.asc` are the same as the file, making sure the file has not been corrupted. | ||
However, now you want to make sure that Nicolas Dorier signed the binaries. | ||
|
||
Nicolas Dorier has a [keybase](https://keybase.io/NicolasDorier) account that allow you to verify that his identity is linked to several well-known social media accounts. | ||
And as you can see on his profile page, the PGP key `223F DA69 DEBE A82D` is linked to his keybase identity. | ||
|
||
You can import this key from keybase: | ||
|
||
```bash | ||
curl https://keybase.io/nicolasdorier/pgp_keys.asc?fingerprint=015b4c837b245509e4ac8995223fda69debea82d | gpg --import | ||
``` | ||
|
||
Then you can finally check the hashes: | ||
```bash | ||
gpg2 --verify SHA256SUMS.asc | ||
``` | ||
|
||
Which should output something like: | ||
|
||
``` | ||
gpg: Signature made Tue Nov 26 12:01:06 2019 JST | ||
gpg: using RSA key 223FDA69DEBEA82D | ||
gpg: Good signature from "Nicolas Dorier <[email protected]>" [unknown] | ||
gpg: WARNING: This key is not certified with a trusted signature! | ||
gpg: There is no indication that the signature belongs to the owner. | ||
Primary key fingerprint: 015B 4C83 7B24 5509 E4AC 8995 223F DA69 DEBE A82D | ||
``` |