summaryrefslogtreecommitdiffstats
path: root/test/util/vercmptest.sh
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2017-09-13 05:57:32 +0200
committerAllan McRae <allan@archlinux.org>2017-09-13 06:20:35 +0200
commit39319c1860d200a9b4a3cc2c6975e3cece502f2d (patch)
treecf683fb6978a2921aab35b6f663d48a7775009a6 /test/util/vercmptest.sh
parent64b7edd2fed122e63abd42dbe392a6f2896a0c16 (diff)
downloadpacman-39319c1860d200a9b4a3cc2c6975e3cece502f2d.tar.gz
pacman-39319c1860d200a9b4a3cc2c6975e3cece502f2d.tar.xz
libmakepkg: check for invalid tags in git
As per https://lists.archlinux.org/pipermail/arch-general/2017-July/043876.html git doesn't check that the tag name matches what an annotated tag object *thinks* it should be called. This is a bit of a theoretical attack and some would argue that we should always use commits since upstream can legitimately change a tag, but nevertheless this can result in a downgrade attack if the git download transport was manipulated or the upstream repository hacked. So, check the tag blob to make sure the tag actually matches the name we used for `git checkout`. This really should be fixed in git itself, rather than forcing all downstream users of git verify-tag to implement their own checks, but the git developers disagree, see the discussion surrounding https://public-inbox.org/git/xmqqk2hzldx8.fsf@gitster.mtv.corp.google.com/ Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'test/util/vercmptest.sh')
0 files changed, 0 insertions, 0 deletions