From bf6cdbb6d54942893b5d592f092c27d8bb8fb33a Mon Sep 17 00:00:00 2001
From: Myles Borins <myles.borins@gmail.com>
Date: Mon, 24 Oct 2016 12:03:53 -0400
Subject: [PATCH] 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 while around short keys.
---
 tools/release.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/release.sh b/tools/release.sh
index 397d3d466df785..1151b6dd68d510 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'