fetch-release: fix signature verification!
nix-bitcoin tests / build_test_drivers (push) Canceled after 0s
nix-bitcoin tests / check_flake (push) Canceled after 0s
nix-bitcoin tests / test_scenario (default) (push) Canceled after 0s
nix-bitcoin tests / test_scenario (joinmarket-bitcoind-29) (push) Canceled after 0s
nix-bitcoin tests / test_scenario (netns) (push) Canceled after 0s
nix-bitcoin tests / test_scenario (netnsRegtest) (push) Canceled after 0s
nix-bitcoin tests / build_test_drivers (push) Canceled after 0s
nix-bitcoin tests / check_flake (push) Canceled after 0s
nix-bitcoin tests / test_scenario (default) (push) Canceled after 0s
nix-bitcoin tests / test_scenario (joinmarket-bitcoind-29) (push) Canceled after 0s
nix-bitcoin tests / test_scenario (netns) (push) Canceled after 0s
nix-bitcoin tests / test_scenario (netnsRegtest) (push) Canceled after 0s
`gpg --verify nar-hash.txt.asc` with a single argument lets gpg pick the verification mode from the file's packet structure. For a real detached signature it hashes the sibling nar-hash.txt, but for an inline signed message it verifies the payload embedded in the .asc itself, never reads nar-hash.txt, prints "not a detached signature; file was NOT verified!" and still exits 0. The `&> /dev/null` hid that warning.
This commit is contained in:
@@ -31,7 +31,7 @@ curl -fsS -L -O "$baseUrl/nar-hash.txt"
|
|||||||
curl -fsS -L -O "$baseUrl/nar-hash.txt.asc"
|
curl -fsS -L -O "$baseUrl/nar-hash.txt.asc"
|
||||||
|
|
||||||
# Verify signature for nar-hash
|
# Verify signature for nar-hash
|
||||||
gpg --verify nar-hash.txt.asc &> /dev/null || {
|
gpg --verify nar-hash.txt.asc nar-hash.txt &> /dev/null || {
|
||||||
>&2 echo "Error: Signature verification failed. Please open an issue in the project repository."
|
>&2 echo "Error: Signature verification failed. Please open an issue in the project repository."
|
||||||
exit 1
|
exit 1
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user