From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v3 20/21] signed push: add "pushee" header to push certificate
Date: Thu, 4 Sep 2014 13:04:56 -0700 [thread overview]
Message-ID: <1409861097-19151-21-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <1409861097-19151-1-git-send-email-gitster@pobox.com>
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>
---
Documentation/technical/pack-protocol.txt | 6 ++++++
send-pack.c | 5 +++++
send-pack.h | 1 +
transport.c | 1 +
4 files changed, 13 insertions(+)
diff --git a/Documentation/technical/pack-protocol.txt b/Documentation/technical/pack-protocol.txt
index 4a5c2e8..7b543dc 100644
--- a/Documentation/technical/pack-protocol.txt
+++ b/Documentation/technical/pack-protocol.txt
@@ -484,6 +484,7 @@ references.
push-cert = PKT-LINE("push-cert" NUL capability-list LF)
PKT-LINE("certificate version 0.1" LF)
PKT-LINE("pusher" SP ident LF)
+ PKT-LINE("pushee" SP url LF)
PKT-LINE(LF)
*PKT-LINE(command LF)
*PKT-LINE(gpg-signature-lines LF)
@@ -527,6 +528,11 @@ Currently, the following header fields are defined:
Identify the GPG key in "Human Readable Name <email@address>"
format.
+`pushee` url::
+ The repository URL (anonymized, if the URL contains
+ authentication material) the user who ran `git push`
+ intended to push into.
+
The GPG signature lines are a detached signature for the contents
recorded in the push certificate before the signature block begins.
The detached signature is used to certify that the commands were
diff --git a/send-pack.c b/send-pack.c
index 61f321d..642ebc8 100644
--- a/send-pack.c
+++ b/send-pack.c
@@ -240,6 +240,11 @@ static int generate_push_cert(struct strbuf *req_buf,
datestamp(stamp, sizeof(stamp));
strbuf_addf(&cert, "certificate version 0.1\n");
strbuf_addf(&cert, "pusher %s %s\n", signing_key, stamp);
+ if (args->url && *args->url) {
+ char *anon_url = transport_anonymize_url(args->url);
+ strbuf_addf(&cert, "pushee %s\n", anon_url);
+ free(anon_url);
+ }
strbuf_addstr(&cert, "\n");
for (ref = remote_refs; ref; ref = ref->next) {
diff --git a/send-pack.h b/send-pack.h
index 3555d8e..5635457 100644
--- a/send-pack.h
+++ b/send-pack.h
@@ -2,6 +2,7 @@
#define SEND_PACK_H
struct send_pack_args {
+ const char *url;
unsigned verbose:1,
quiet:1,
porcelain:1,
diff --git a/transport.c b/transport.c
index 07fdf86..1df1375 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);
--
2.1.0-399-g1364b4d
next prev parent reply other threads:[~2014-09-04 20:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 20:04 [PATCH v3 00/21] Signed push Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 01/21] receive-pack: do not overallocate command structure Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 02/21] receive-pack: parse feature request a bit earlier Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 03/21] receive-pack: do not reuse old_sha1[] for other things Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 04/21] receive-pack: factor out queueing of command Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 05/21] send-pack: move REF_STATUS_REJECT_NODELETE logic a bit higher Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 06/21] send-pack: refactor decision to send update per ref Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 07/21] send-pack: always send capabilities Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 08/21] send-pack: factor out capability string generation Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 09/21] receive-pack: " Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 10/21] send-pack: rename "new_refs" to "need_pack_data" Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 11/21] send-pack: refactor inspecting and resetting status and sending commands Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 12/21] send-pack: clarify that cmds_sent is a boolean Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 13/21] gpg-interface: move parse_gpg_output() to where it should be Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 14/21] gpg-interface: move parse_signature() " Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 15/21] pack-protocol doc: typofix for PKT-LINE Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 16/21] push: the beginning of "git push --signed" Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 17/21] receive-pack: GPG-validate push certificates Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 18/21] send-pack: send feature request on push-cert packet Junio C Hamano
2014-09-04 20:04 ` [PATCH v3 19/21] signed push: remove duplicated protocol info Junio C Hamano
2014-09-04 20:04 ` Junio C Hamano [this message]
2014-09-04 21:13 ` [PATCH v3 20/21] signed push: add "pushee" header to push certificate Shawn Pearce
2014-09-04 20:04 ` [PATCH v3 21/21] signed push: fortify against replay attacks Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1409861097-19151-21-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).