From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: The git protocol and DoS
Date: Wed, 19 Oct 2005 14:59:25 -0700 [thread overview]
Message-ID: <4356C1BD.5060806@zytor.com> (raw)
In-Reply-To: <7vek6h43oj.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
>
>>You mean an option on the *server* to skip the cookie exchange? If so,
>>how would you expect the client to handle it?
>
> No, what I was thinking was to tell the client "you will be
> talking to an old server, so do not try to read that cookie and
> get stuck".
>
Oh, right.
-hpa
next prev parent reply other threads:[~2005-10-19 21:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 20:00 The git protocol and DoS H. Peter Anvin
2005-10-19 20:50 ` Junio C Hamano
2005-10-19 20:55 ` H. Peter Anvin
2005-10-19 21:06 ` Junio C Hamano
2005-10-19 21:59 ` H. Peter Anvin [this message]
2005-10-19 21:31 ` Linus Torvalds
2005-10-19 21:54 ` Junio C Hamano
2005-10-19 22:01 ` H. Peter Anvin
2005-10-19 22:20 ` Petr Baudis
2005-10-19 22:39 ` Tony Luck
2005-10-20 0:20 ` David Brown
2005-10-20 8:16 ` Andreas Ericsson
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=4356C1BD.5060806@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).