Revisions to How can I check the integrity of a Bitcoin tarball with GPG?

urge the users: Do not continue, if it does not match! (fingerprint)

Source Link

edited Feb 4, 2018 at 11:47

1.7k
3
22
41

Updated for the latest version: 0.15.1

You need to verify the signing key's fingerprint, before you import it:

 cat laanwj-releases.asc | gpg --with-fingerprint --with-colons - | sed -ne 's|^fpr:::::::::\([0-9A-F]\+\):$|\1|p'

It should say:

>     01EA5486DE18A882D4C2684590C8019E36C2E964

Do not continue, if it does not match!

The signing key needs to be imported:

 gpg --import laanwj-releases.asc 2>&1 | grep 36C2E964

It should say:

>     gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported

Now, we check the hash sum containing file's signature:
```
 gpg --verify SHA256SUMS.asc
```

It should say:

>     gpg: Signature made Sat 11 Nov 2017 02:52:22 PM CET using RSA key ID 36C2E964
    gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>"

And finally what we needed - to check that the hash sum of the file matches:
```
 sha256sum --check --ignore-missing SHA256SUMS.asc 2>&1 | grep OK
```

It should say:

>     bitcoin-0.15.1-x86_64-linux-gnu.tar.gz: OK

In case it does not output anything, something's wrong and you may verify this by running it without `| grep OK` on the end.

Updated for the latest version: 0.15.1

You need to verify the signing key's fingerprint, before you import it:

 cat laanwj-releases.asc | gpg --with-fingerprint --with-colons - | sed -ne 's|^fpr:::::::::\([0-9A-F]\+\):$|\1|p'

It should say:

>     01EA5486DE18A882D4C2684590C8019E36C2E964

The signing key needs to be imported:

 gpg --import laanwj-releases.asc 2>&1 | grep 36C2E964

It should say:

>     gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported

Now, we check the hash sum containing file's signature:
```
 gpg --verify SHA256SUMS.asc
```

It should say:

>     gpg: Signature made Sat 11 Nov 2017 02:52:22 PM CET using RSA key ID 36C2E964
    gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>"

And finally what we needed - to check that the hash sum of the file matches:
```
 sha256sum --check --ignore-missing SHA256SUMS.asc 2>&1 | grep OK
```

It should say:

>     bitcoin-0.15.1-x86_64-linux-gnu.tar.gz: OK

In case it does not output anything, something's wrong and you may verify this by running it without `| grep OK` on the end.

Updated for the latest version: 0.15.1

You need to verify the signing key's fingerprint, before you import it:

 cat laanwj-releases.asc | gpg --with-fingerprint --with-colons - | sed -ne 's|^fpr:::::::::\([0-9A-F]\+\):$|\1|p'

It should say:

>     01EA5486DE18A882D4C2684590C8019E36C2E964

Do not continue, if it does not match!

The signing key needs to be imported:

 gpg --import laanwj-releases.asc 2>&1 | grep 36C2E964

It should say:

>     gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported

Now, we check the hash sum containing file's signature:
```
 gpg --verify SHA256SUMS.asc
```

It should say:

>     gpg: Signature made Sat 11 Nov 2017 02:52:22 PM CET using RSA key ID 36C2E964
    gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>"

And finally what we needed - to check that the hash sum of the file matches:
```
 sha256sum --check --ignore-missing SHA256SUMS.asc 2>&1 | grep OK
```

It should say:

>     bitcoin-0.15.1-x86_64-linux-gnu.tar.gz: OK

In case it does not output anything, something's wrong and you may verify this by running it without `| grep OK` on the end.

You need to verify the signing key's fingerprint, before you import it:

Source Link

edited Feb 4, 2018 at 8:57

Vlastimil Burián

1.7k
3
22
41

Updated for the latest version: 0.15.1

The signing key needsYou need to be importedverify the signing key's fingerprint, before you import it:

 gpg --importcat laanwj-releases.asc 2>&1| gpg --with-fingerprint --with-colons - | grepsed 36C2E964-ne 's|^fpr:::::::::\([0-9A-F]\+\):$|\1|p'

It should say:

>     gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported01EA5486DE18A882D4C2684590C8019E36C2E964

You needThe signing key needs to verify its fingerprintbe imported:

 cat laanwj-releases.asc | gpg --with-fingerprintimport --withlaanwj-colonsreleases.asc -2>&1 | sed -negrep 's|^fpr:::::::::\([0-9A-F]\+\):$|\1|p'36C2E964

It should say:

>     01EA5486DE18A882D4C2684590C8019E36C2E964gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported

Now, we check the hash sum containing file's signature:
```
 gpg --verify SHA256SUMS.asc
```

It should say:

>     gpg: Signature made Sat 11 Nov 2017 02:52:22 PM CET using RSA key ID 36C2E964
    gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>"

And finally what we needed - to check that the hash sum of the file matches:
```
 sha256sum --check --ignore-missing SHA256SUMS.asc 2>&1 | grep OK
```

It should say:

>     bitcoin-0.15.1-x86_64-linux-gnu.tar.gz: OK

In case it does not output anything, something's wrong and you may verify this by running it without `| grep OK` on the end.

Updated for the latest version: 0.15.1

The signing key needs to be imported:

 gpg --import laanwj-releases.asc 2>&1 | grep 36C2E964

It should say:

>     gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported

You need to verify its fingerprint:

 cat laanwj-releases.asc | gpg --with-fingerprint --with-colons - | sed -ne 's|^fpr:::::::::\([0-9A-F]\+\):$|\1|p'

It should say:

>     01EA5486DE18A882D4C2684590C8019E36C2E964

Now, we check the hash sum containing file's signature:
```
 gpg --verify SHA256SUMS.asc
```

It should say:

>     gpg: Signature made Sat 11 Nov 2017 02:52:22 PM CET using RSA key ID 36C2E964
    gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>"

And finally what we needed - to check that the hash sum of the file matches:
```
 sha256sum --check --ignore-missing SHA256SUMS.asc 2>&1 | grep OK
```

It should say:

>     bitcoin-0.15.1-x86_64-linux-gnu.tar.gz: OK

In case it does not output anything, something's wrong and you may verify this by running it without `| grep OK` on the end.

Updated for the latest version: 0.15.1

You need to verify the signing key's fingerprint, before you import it:

 cat laanwj-releases.asc | gpg --with-fingerprint --with-colons - | sed -ne 's|^fpr:::::::::\([0-9A-F]\+\):$|\1|p'

It should say:

>     01EA5486DE18A882D4C2684590C8019E36C2E964

The signing key needs to be imported:

 gpg --import laanwj-releases.asc 2>&1 | grep 36C2E964

It should say:

>     gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported

Now, we check the hash sum containing file's signature:
```
 gpg --verify SHA256SUMS.asc
```

It should say:

>     gpg: Signature made Sat 11 Nov 2017 02:52:22 PM CET using RSA key ID 36C2E964
    gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>"

And finally what we needed - to check that the hash sum of the file matches:
```
 sha256sum --check --ignore-missing SHA256SUMS.asc 2>&1 | grep OK
```

It should say:

>     bitcoin-0.15.1-x86_64-linux-gnu.tar.gz: OK

In case it does not output anything, something's wrong and you may verify this by running it without `| grep OK` on the end.

better code

Source Link

edited Feb 4, 2018 at 8:18

Vlastimil Burián

1.7k
3
22
41

Updated for the latest version: 0.15.1

The signing key needs to be imported:

 gpg --import laanwj-releases.asc 2>&1 | grep 36C2E964

It should say:

>     gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported

You need to verify its fingerprint:

 cat laanwj-releases.asc | gpg --with-fingerprint 36C2E964--with-colons - | grepsed fingerprint-ne 's|^fpr:::::::::\([0-9A-F]\+\):$|\1|p'

It should say:

>     Key fingerprint = 01EA 5486 DE18 A882 D4C2  6845 90C8 019E 36C2 E96401EA5486DE18A882D4C2684590C8019E36C2E964

Now, we check the hash sum containing file's signature:
```
 gpg --verify SHA256SUMS.asc 2>&1 | grep Good
```

It should say:

>     gpg: Good signature fromSignature "Wladimirmade J.Sat van11 derNov Laan2017 (Bitcoin02:52:22 CorePM binaryCET releaseusing signingRSA key) <[email protected]>"

In case it doesID not36C2E964
 output anything, something's wronggpg: andGood yousignature mayfrom verify"Wladimir thisJ. byvan runningder itLaan without(Bitcoin `|Core grepbinary Good`release onsigning thekey) end<laanwj@gmail.com>"

And finally what we needed - to check that the hash sum of the file matches:
```
 sha256sum --check --ignore-missing SHA256SUMS.asc 2>&1 | grep OK
```

It should say:

>     bitcoin-0.15.1-x86_64-linux-gnu.tar.gz: OK

In case it does not output anything, something's wrong and you may verify this by running it without `| grep OK` on the end.

Updated for the latest version: 0.15.1

The signing key needs to be imported:

 gpg --import laanwj-releases.asc 2>&1 | grep 36C2E964

It should say:

>     gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported

You need to verify its fingerprint:

 gpg --fingerprint 36C2E964 | grep fingerprint

It should say:

>     Key fingerprint = 01EA 5486 DE18 A882 D4C2  6845 90C8 019E 36C2 E964

Now, we check the hash sum containing file's signature:
```
 gpg --verify SHA256SUMS.asc 2>&1 | grep Good
```

It should say:

>     gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>"

In case it does not output anything, something's wrong and you may verify this by running it without `| grep Good` on the end.

And finally what we needed - to check that the hash sum of the file matches:
```
 sha256sum --check --ignore-missing SHA256SUMS.asc 2>&1 | grep OK
```

It should say:

>     bitcoin-0.15.1-x86_64-linux-gnu.tar.gz: OK

In case it does not output anything, something's wrong and you may verify this by running it without `| grep OK` on the end.

Updated for the latest version: 0.15.1

The signing key needs to be imported:

 gpg --import laanwj-releases.asc 2>&1 | grep 36C2E964

It should say:

>     gpg: key 36C2E964: "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <[email protected]>" imported

You need to verify its fingerprint:

 cat laanwj-releases.asc | gpg --with-fingerprint --with-colons - | sed -ne 's|^fpr:::::::::\([0-9A-F]\+\):$|\1|p'

It should say:

>     01EA5486DE18A882D4C2684590C8019E36C2E964

Now, we check the hash sum containing file's signature:
```
 gpg --verify SHA256SUMS.asc
```

It should say:

>     gpg: Signature made Sat 11 Nov 2017 02:52:22 PM CET using RSA key ID 36C2E964
    gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <laanwj@gmail.com>"

And finally what we needed - to check that the hash sum of the file matches:
```
 sha256sum --check --ignore-missing SHA256SUMS.asc 2>&1 | grep OK
```

It should say:

>     bitcoin-0.15.1-x86_64-linux-gnu.tar.gz: OK

In case it does not output anything, something's wrong and you may verify this by running it without `| grep OK` on the end.

updated to version 0.15.1

Source Link

edited Nov 19, 2017 at 11:55

Vlastimil Burián

1.7k
3
22
41

Loading

grepping good outputs, better for reading the outputs overall

Source Link

edited Apr 27, 2017 at 8:16

Vlastimil Burián

1.7k
3
22
41

Loading

Updated for the latest version: 0.14.0

Source Link

edited Mar 13, 2017 at 10:41

Vlastimil Burián

1.7k
3
22
41

Loading

deleted 88 characters in body

Source Link

edited Mar 8, 2017 at 10:09

Vlastimil Burián

1.7k
3
22
41

Loading

Updated for the latest versions: Bitcoin Core 0.13.2

Source Link

edited Mar 8, 2017 at 10:02

Vlastimil Burián

1.7k
3
22
41

Loading

improved formatting

Source Link

edit approved May 27, 2016 at 1:49

techraf

9.2k
11
46
63

Loading

Source Link

created May 27, 2016 at 0:49

Vlastimil Burián

1.7k
3
22
41

Loading

Stack Exchange Network

Return to Answer

Updated for the latest version: 0.15.1

Updated for the latest version: 0.15.1

Updated for the latest version: 0.15.1

Updated for the latest version: 0.15.1

Updated for the latest version: 0.15.1

Updated for the latest version: 0.15.1

Updated for the latest version: 0.15.1

Updated for the latest version: 0.15.1

Updated for the latest version: 0.15.1