aboutsummaryrefslogtreecommitdiff
path: root/transport.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-08-22 18:15:24 -0700
committerJunio C Hamano <gitster@pobox.com>2014-09-15 13:23:28 -0700
commit9be89160e7382a88e56a02bcf38f4694dd6542d6 (patch)
treed321807664e8398eb5c99c1dc7a08cccdfd82c77 /transport.c
parent4adf569dea052dac88121d822e11c249986b3398 (diff)
downloadgit-9be89160e7382a88e56a02bcf38f4694dd6542d6.tar.gz
git-9be89160e7382a88e56a02bcf38f4694dd6542d6.tar.xz
signed push: add "pushee" header to push certificate
Record the URL of the intended recipient for a push (after anonymizing it if it has authentication material) on a new "pushee URL" header. Because the networking configuration (SSH-tunnels, proxies, etc.) on the pushing user's side varies, the receiving repository may not know the single canonical URL all the pushing users would refer it as (besides, many sites allow pushing over ssh://host/path and https://host/path protocols to the same repository but with different local part of the path). So this value may not be reliably used for replay-attack prevention purposes, but this will still serve as a human readable hint to identify the repository the certificate refers to. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'transport.c')
-rw-r--r--transport.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/transport.c b/transport.c
index 07fdf8649..1df13753a 100644
--- a/transport.c
+++ b/transport.c
@@ -827,6 +827,7 @@ static int git_transport_push(struct transport *transport, struct ref *remote_re
args.dry_run = !!(flags & TRANSPORT_PUSH_DRY_RUN);
args.porcelain = !!(flags & TRANSPORT_PUSH_PORCELAIN);
args.push_cert = !!(flags & TRANSPORT_PUSH_CERT);
+ args.url = transport->url;
ret = send_pack(&args, data->fd, data->conn, remote_refs,
&data->extra_have);