Re: Performance issue: initial git clone causes massive repack

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 15, 2009, 05:54 UTC
Message-ID: <7vljq2zckw.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <fcaeb9bf0904142009w5a21e483v7e98f91e5e35b14a@mail.gmail.com>

Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:

>> 2. Disallow initial clones over git:// (allow updates ONLY)
>
> How can you do that? If I understand git protocol correctly, there is
> no difference between a fetch request and a clone one.

At the protocol level, you can tell a clone request by noticing that the downloading side does not have any "have" lines, but it is a different matter what the software does out of the box.

You can patch upload-pack to reject such requests. I am sure gentoo folks are capable of doing that ;-)

Also a rogue client can send a bogus "have" to fool that logic, and that is the primary reason why we do not have such a patch to upload-pack. It is not worth it as a protection against determined people who want to DoS.