summaryrefslogtreecommitdiff
path: root/.travis.yml
diff options
context:
space:
mode:
authorJonathan Tan <jonathantanmy@google.com>2017-05-09 19:23:53 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-05-10 04:18:28 (GMT)
commitcbaf82cc6b734244a9190c3341ca5f08f8d5acc4 (patch)
treeb06badfc81d2b16f22715a4f8b33dc40523a6719 /.travis.yml
parentb7b744f297b736c51636407f5883b3777bb36433 (diff)
downloadgit-cbaf82cc6b734244a9190c3341ca5f08f8d5acc4.zip
git-cbaf82cc6b734244a9190c3341ca5f08f8d5acc4.tar.gz
git-cbaf82cc6b734244a9190c3341ca5f08f8d5acc4.tar.bz2
receive-pack: verify push options in cert
In commit f6a4e61 ("push: accept push options", 2016-07-14), send-pack was taught to include push options both within the signed cert (if the push is a signed push) and outside the signed cert; however, receive-pack ignores push options within the cert, only handling push options outside the cert. Teach receive-pack, in the case that push options are provided for a signed push, to verify that the push options both within the cert and outside the cert are consistent. This sets in stone the requirement that send-pack redundantly send its push options in 2 places, but I think that this is better than the alternatives. Sending push options only within the cert is backwards-incompatible with existing Git servers (which read push options only from outside the cert), and sending push options only outside the cert means that the push options are not signed for. Signed-off-by: Jonathan Tan <jonathantanmy@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to '.travis.yml')
0 files changed, 0 insertions, 0 deletions