From: Taylor Blau <me@ttaylorr.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] upload-pack: handle unexpected v2 delim packets
Date: Fri, 27 Mar 2020 09:18:29 -0600 [thread overview]
Message-ID: <20200327151829.GA30577@syl.local> (raw)
In-Reply-To: <20200327080210.GA604725@coredump.intra.peff.net>
Hi Peff,
On Fri, Mar 27, 2020 at 04:02:10AM -0400, Jeff King wrote:
> We saw an upload-pack segfault in the wild today at GitHub. It's caused
> by a client sending bogus v2 protocol lines (a "delim" packet instead of
> a "flush"). So the client is broken and our only option is to break the
> network connection, but we shouldn't segfault while doing so. :)
>
> I don't think the broken client was Git. It didn't send an "agent"
> capability at all, which makes me suspect it was somebody generating the
> request manually (nor was there anything interesting in the transport
> layer agent; it was just an openssh client).
>
> The fix was simple enough, and is in the second patch. The first one is
> just a small cleanup / refactor in preparation.
>
> [1/2]: test-lib-functions: make packetize() more efficient
> [2/2]: upload-pack: handle unexpected delim packets
>
> ls-refs.c | 5 +++-
> t/t5562-http-backend-content-length.sh | 19 +++++++++------
> t/t5704-protocol-violations.sh | 33 ++++++++++++++++++++++++++
> t/test-lib-functions.sh | 23 ++++++++++++------
> upload-pack.c | 5 +++-
> 5 files changed, 69 insertions(+), 16 deletions(-)
> create mode 100755 t/t5704-protocol-violations.sh
Thanks. This series looks good to me, and is certainly improving things.
Reviewed-by: Taylor Blau <me@ttaylorr.com>
> -Peff
Thanks,
Taylor
prev parent reply other threads:[~2020-03-27 15:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 8:02 [PATCH 0/2] upload-pack: handle unexpected v2 delim packets Jeff King
2020-03-27 8:03 ` [PATCH 1/2] test-lib-functions: make packetize() more efficient Jeff King
2020-03-27 15:16 ` Taylor Blau
2020-03-28 12:25 ` Jeff King
2020-03-27 19:18 ` Junio C Hamano
2020-03-28 11:20 ` Jeff King
2020-03-29 0:11 ` Junio C Hamano
2020-03-29 3:05 ` Junio C Hamano
2020-03-29 14:53 ` Jeff King
2020-03-29 15:44 ` Junio C Hamano
2020-03-29 14:52 ` Jeff King
2020-03-29 15:02 ` [PATCH] test-lib-functions: simplify packetize() stdin code Jeff King
2020-03-29 15:49 ` Junio C Hamano
2020-03-27 8:03 ` [PATCH 2/2] upload-pack: handle unexpected delim packets Jeff King
2020-03-27 15:17 ` Taylor Blau
2020-03-27 15:18 ` Taylor Blau [this message]
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=20200327151829.GA30577@syl.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).