The case here is that I have to use Smart HTTP because we employ SSO
which works with apache, as our user management works this way. We
have a quite a crowd of developers and access to projects gets managed
within this frame. It seems also to me that speed penalty by using SSL
+ Smart HTTP against GIT or SSH protocol is minimal. Assigning user
name and password to developer is a much easier way to manage them, in
contrast to public key management. I imagine that different scenarios
would play rather better in another environments, but in this case
HTTP is preferred to us.
On Aug 11, 7:21 pm, Konstantin Khomoutov
> On Thu, 11 Aug 2011 07:55:36 -0700 (PDT)
> evilpingus <evilpin...@gmail.com> wrote:
> > I been trying to switch to GIT from SVN, for couple days allready, but
> > cannot overcome this annoying issue with push. I have been googling
> > and trying some suggested ways but still no avail, and I am pretty
> > desparate as I have been taking too much time with this issue
> > allready, so any suggestions, comments would be very very wellcome.
> > I succeed with ssh and git protocol, but in my case only option I can
> > make it work is Smart HTTP.
> > Git repos are located under /var/git/*.git as bare repositories
> An obligatory question someone should ask: is there really any
> compelling reason not to use SSH-based access native to Git?
> It seems you're hosting on a POSIX system anyway so there's no problem
> in setting up SSH-server, and user management for accessing the
> repositories could be implemented using a suitable tool such as gitolite
> or gitosis.
> Windows clients also have no problems with SSH access thanks to PuTTY.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at