At 02:12 AM 11/12/2013, Konstantin Khomoutov wrote:
On Mon, 11 Nov 2013 20:41:51 -0800 (PST)
Ray Tayek <> wrote:
> doing a push origin master got an acces denied or repository not
> exported. so i added --enable=receive-pack to the deamon invocation.

Are you aware that enabling this mode allows everyone to push
arbitrary data into your repository without any authentication?


... no authentication is supported by git-daemon, ...

i understand.

> now push origin master says:
>  counting objects: 3 done
>  writing objects: 100% (3/3)
> and then hangs :(

This is a known bug in Git for Windows [1] which turned out to be
incredibly hard to track down.  Since no one pushes to git-daemon
anyway, the bug is still not fixed.


It has been discovered that disabling a certain feature known as
"side-band-64k" push protocol extension [2] helps (see comments #1 and #2 in [1]).

oh my, looks like deep yogurt to me.

So to help the problem you basically have several options:

1) Host your shared Git repos on a box running an OS "native" to Git, .

that box needs to run windows.

   IMO, in our brave new world full of cheap virtualization, this is
   *the* way to go: just grab an OS [3] and install it in on a
   virtualised server.  A VPS/VDS is also an option.

i may try that if all else fails.

2) Continue to use Windows as a hosting platform but stop using
   git-daemon.  ...

i don't know any iis.

   Another solution is to use gitblit [8] -- it does not use Git for
   Windows on the server at all relying instead on a pure Java library
   called JGit.

i am java guy, i will look into jgit.

3) Build Git for Windows from the source  ...

the reason i am trying to get git up is that i want to fool around with jenkins.

4) Attempt to binary-patch Git [5] to disable the offending feature
   (on the client *or* the server, not on both).

i'll pass on this one.

> git log says: fatal: bad default revision  'HEAD'

You failed to tell us where you're running this -- on the client
or on the server?

running on the server (localhost) in the foo.git repo. and the same thing happens if i try the experiment with two pcs.

thanks for an extremely good answer.



You received this message because you are subscribed to the Google Groups "Git for 
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to