<!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->
<!-- Describe the issue -->
As instructed here:
https://bitcoincore.org/en/download/
the releases (SHA256SUMS file) should be signed by laanwj (01EA5486DE18A882D4C2684590C8019E36C2E964).
pi@raspberrypi $ gpg --keyserver hkp://keyserver.ubuntu.com --refresh-keys
...
gpg: Total number processed: 254
gpg: unchanged: 174
gpg: new user IDs: 45
gpg: new subkeys: 64
gpg: new signatures: 1099
pi@raspberrypi $ gpg --list-keys 01EA5486DE18A882D4C2684590C8019E36C2E964
pub rsa4096 2015-06-24 [SC] [expires: 2022-02-10]
01EA5486DE18A882D4C2684590C8019E36C2E964
uid [ unknown] Wladimir J. van der Laan (Bitcoin Core binary release signing key) <laanwj@gmail.com>
pi@raspberrypi $ sha256sum bitcoin-22.0-x86_64-linux-gnu.tar.gz
59ebd25dd82a51638b7a6bb914586201e67db67b919b2a1ff08925a7936d1b16 bitcoin-22.0-x86_64-linux-gnu.tar.gz
pi@raspberrypi $ grep 59ebd25dd82a51638b7a6bb914586201e67db67b919b2a1ff08925a7936d1b16 SHA256SUMS
59ebd25dd82a51638b7a6bb914586201e67db67b919b2a1ff08925a7936d1b16 bitcoin-22.0-x86_64-linux-gnu.tar.gz
pi@raspberrypi $ gpg --verify SHA256SUMS.asc SHA256SUMS 2>&1 | grep -i -e 01EA5486DE18A882D4C2684590C8019E36C2E964 -e laanwj@gmail.com -e 0CCBAAFD76A2ECE2CCD3141DE2FFD5B1D88CA97D
gpg: using RSA key 0CCBAAFD76A2ECE2CCD3141DE2FFD5B1D88CA97D
Expected behavior
I expected to see laanwj key id or email address in the output of the gpg SHA256SUMS.asc verification.
Actual behavior
The laanwj key was not indicated as having signed SHA256SUMS.asc (I added the other id 0CCBAAFD76A2ECE2CCD3141DE2FFD5B1D88CA97D as a test).
To reproduce
gpg --keyserver hkp://keyserver.ubuntu.com --refresh-key
gpg --list-keys 01EA5486DE18A882D4C2684590C8019E36C2E964
wget https://bitcoincore.org/bin/bitcoin-core-22.0/bitcoin-22.0-x86_64-linux-gnu.tar.gz
sha256sum bitcoin-22.0-x86_64-linux-gnu.tar.gz
wget https://bitcoincore.org/bin/bitcoin-core-22.0/SHA256SUMS.asc
wget https://bitcoincore.org/bin/bitcoin-core-22.0/SHA256SUMS
gpg --verify SHA256SUMS.asc 2>&1 | grep -i -e 01EA5486DE18A882D4C2684590C8019E36C2E964 -e laanwj@gmail.com -e 0CCBAAFD76A2ECE2CCD3141DE2FFD5B1D88CA97
System information
<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->
bitcoin-22.0-x86_64-linux-gnu
wget https://bitcoincore.org/bin/bitcoin-core-22.0/SHA256SUMS.asc
<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
raspberry pi
<!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->
not gui related
<!-- Any extra information that might be useful in the debugging process. -->
<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->
