summaryrefslogtreecommitdiff
path: root/tools/release.sh
diff options
context:
space:
mode:
authorMyles Borins <myles.borins@gmail.com>2016-10-24 12:03:53 -0400
committerMyles Borins <myles.borins@gmail.com>2016-11-07 10:34:10 -0500
commitb315e2455e5121b6551c17bc7793ef0a101080f7 (patch)
tree581fc5233b088273108515fef502f5743f40b3de /tools/release.sh
parenta5045167823e4c02a0d6343304a2832514e7a9a7 (diff)
downloadandroid-node-v8-b315e2455e5121b6551c17bc7793ef0a101080f7.tar.gz
android-node-v8-b315e2455e5121b6551c17bc7793ef0a101080f7.tar.bz2
android-node-v8-b315e2455e5121b6551c17bc7793ef0a101080f7.zip
tools: use long format for gpg fingerprint
Git has been using my Long format fingerprint in the tagging messages, this has been causing the release script to fail on my keys. It would also be wise to be using the long format on keys based on some attacks that hack been found in the wild around short keys. PR-URL: https://github.com/nodejs/node/pull/9258 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
Diffstat (limited to 'tools/release.sh')
-rwxr-xr-xtools/release.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/release.sh b/tools/release.sh
index 397d3d466d..1151b6dd68 100755
--- a/tools/release.sh
+++ b/tools/release.sh
@@ -50,7 +50,7 @@ elif [ $keycount -ne 1 ]; then
done
fi
-gpgfing=$(gpg --fingerprint $gpgkey | grep 'Key fingerprint =' | awk -F' = ' '{print $2}' | tr -d ' ')
+gpgfing=$(gpg --keyid-format 0xLONG --fingerprint $gpgkey | grep 'Key fingerprint =' | awk -F' = ' '{print $2}' | tr -d ' ')
if ! test "$(grep $gpgfing README.md)"; then
echo 'Error: this GPG key fingerprint is not listed in ./README.md'