How to configure git server WITHOUT ssh auth

Some time ago, I came across an explanation of how to somehow configure git authentication through a web server. Thus, on the client side, ssh key exchange is not required.
Shame on me, I did not mortgage his link and do not remember the technique.

I just miss throwing username: password to provide access to some backup storage. When prototyping some VM installations, this was the last time I felt this need, snapshots were not an ideal solution.

Is it possible to use git only with password based authorization?

Another use case I’ve heard will be at a university where this approach is a less organizational overhead for creating new accounts for 30 people each semester. Imagine that you are collecting ssh keys from a group of people who have problems creating their own key pair, not even talking about people who do not know what VCS is or what it is used for.

Of course, the solution to this would be to simply use SVN for version control. But do I need to use SVN when you can have git?

To prevent misunderstandings, I have my own server running a running gitolite installation, and I am doing a great job using ssh keys for clients and servers.

+4
source share
1 answer

You can use gitolite with any service that can provide authentication (therefore it excludes the git protocol, which does not have authentication).

My https configuration will invoke gitolite with an identifier that Apache will provide a gitolit script.

ScriptAlias /hgit/ @ H@ /sbin/gitolite-shell/ SetEnv GIT_HTTP_BACKEND "@ H@ /usr/local/apps/git/libexec/git-core/git-http-backend" <Location /hgit> ... </Location> 
+2
source

All Articles