Commit 6e5906c
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 <bugs@bergstroem.nu>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rod Vagg <rod@vagg.org>1 parent 612dfeb commit 6e5906c
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -50,7 +50,7 @@ elif [ $keycount -ne 1 ]; then | |||
| 50 | 50 | done | |
| 51 | 51 | fi | |
| 52 | 52 | ||
| 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 ' ') | ||
| 54 | 54 | ||
| 55 | 55 | if ! test "$(grep $gpgfing README.md)"; then | |
| 56 | 56 | echo 'Error: this GPG key fingerprint is not listed in ./README.md' | |
0 commit comments