Skip to content

Commit 8b85d47

Browse files
committed
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: #9258 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
1 parent 0fcf249 commit 8b85d47

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

tools/release.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ elif [ $keycount -ne 1 ]; then
5050
done
5151
fi
5252

53-
gpgfing=$(gpg --fingerprint $gpgkey | grep 'Key fingerprint =' | awk -F' = ' '{print $2}' | tr -d ' ')
53+
gpgfing=$(gpg --keyid-format 0xLONG --fingerprint $gpgkey | grep 'Key fingerprint =' | awk -F' = ' '{print $2}' | tr -d ' ')
5454

5555
if ! test "$(grep $gpgfing README.md)"; then
5656
echo 'Error: this GPG key fingerprint is not listed in ./README.md'

0 commit comments

Comments
 (0)