Cannot clone gitolite 3 gitolite-admin with Tortoisegit on WIndows 7

gitolite

I've installed Gotolite 3 on my CentOS 6.2 (64-bit) system using yum, and am trying to clone gitolite-admin with Tortoisegit on Windows 7 (64-bit), which I installed with PLink. Tortoisegit just says it's cloning but the progress bar never moves and no files ever show up in folder glssh.html, until finally it aborts with an error 128 (HTTP request failed, git did not exit cleanly).

The ~gitolite3/.ssh/suthorized_keys looks like this:

# gitolite start
command="/usr/share/gitolite3/gitolite-shell gitkey",no-port-forwarding,no-X11-     forwarding,no-agent-forwarding,no-pty ssh-rsa  AAAAB3NzaC1yc2EAAAABJQAAAIEAozy1qK68k2iu6rTJHNifMMne9DXvsm/pSeqMprRqJAdtLNHLxsFoPT7JF8Ct5GLbyZRWzV4tGjPnp7LJjsodMrjKes5km4LO1Q4tZPisdQu/awYkz8gg54sBwyJPlaIoL8pvMlzot+ZfcMwBm7Amgs5zEgqn4p+vVtqoOyh/sPk= Gitolite Admin
# gitolite end
ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAIBpO6jH4BPN8KwSZHEtG6kvkmWT/WZbtWSzpkklOjHrc1qu+pT0QHR1NfM8/pxOodbKoSmxUC1iaMVvhmURK4FFPJvvCIhUPud01BYCffjuBcYIYr1lfGwWVWc8Wvqg3DGkjL4bVEIYGx6gsg8OmLDMqzjXYuTW/yt6gKoEBs5oMw== Gitolite Account Key

I had a lot of trouble getting Tortoise (or Git bash) from prompting me for a password, but I don't think the keys are the problem anymore. I assume the gitolite-shell command is getting triggered, or Tortoise would just fail immediately like it does with the other (shell account) key. Is the problem now on the server side? The instructions for installing from the RPM were pretty sketchy (and neglected to mention anything like gitolite setup -pk to install a key to begin with.

Best Answer

You need to set in etc/ssh/sshd_config

PasswordAuthentication no

Match User yourUser
        PasswordAuthentication no

That should solve the asking for password Problem.

Now Selinux is going to complain https://bugzilla.redhat.com/show_bug.cgi?id=827389
To check this
On your gitolite-server

[root@centos63 ~]# setenforce 0

On your gitolite admin account

ssh yourUser@yourBox info
#Should be the answer message
hello admin, this is yourUser@yourBox running gitolite3 3.04-1.el6 on git 1.7.1

 R W    gitolite-admin
 R W    testing

Set your Selinux back to enforcing mode

[root@centos63 ~]# setenforce 1

and do a ssh yourUser@yourBox info if you dont get the same message as before you need to update your Selinux-Policies

Install this updates

selinux-policy-3.7.19-159
selinux-policy-targeted-3.7.19-159

I got them from http://people.redhat.com/dwalsh/SELinux/RHEL6/noarch/
The Problem should be gone.

Related Solutions

Gitolite Clone Issues – How to Fix Gitolite Clone Not Working on Debian

Being able to access gitolite@server:~/repositories/gitolite-admin.git, but not gitolite@server:gitolite-admin indicates you are not going “through” Gitolite, but just using plain SSH-based access to the gitolite user.

If ssh gitolite@server echo normal access yields normal access, then the key you are using is not restricted to going through Gitolite. If you were going through Gitolite you would see something like bad command: echo normal access.

This can happen if you have a key that you use to SSH into the gitolite user itself and you try to use that same key to authenticate as a Gitolite user. A “normal access” key will be present in gitolite’s .ssh/authorized_keys without any special prefix. The line for a key that is configured to go through Gitolite will start like command="/path/to/gl-auth-command gitolite-username",….

If you need normal SSH-based access to the gitolite user and Gitolite-based access, then you should setup separate keys for those purposes so that you can specify which key you want to use with IdentityFile options in your .ssh/config file (maybe also IdentitiesOnly if you find that ssh is using the “wrong” key just because you already have it loaded in your ssh-agent).

For example:

Use one of your “default” keys (one of ssh’s defaults (e.g. ~/.ssh/id_rsa) or some key that you usually have loaded in your ssh-agent) to access Gitolite (i.e. you have the public key in the active keydir/your-gitolite-user-name.pub).

Generate ~/.ssh/gitolite-user for use in directly logging into the gitolite user. Use ssh -i ~/.ssh/gitolite-user gitolite@server to login. Or, add a custom entry to ~/.ssh/config:

Host gitolite-user
              User gitolite
          HostName server
      IdentityFile ~/.ssh/gitolite-user
    IdentitiesOnly yes

so you can just do ssh gitolite-user to login.

Can’t clone gitolite-admin

Gitolite 2.x

If git is not in the default PATH, then you can set $GIT_PATH in your gitolite user’s ~/.gitolite.rc.

The default .gitolite.rc comes with this line:

$GIT_PATH="";

If your Git installation is under /usr/local (so that you have /usr/local/bin/git), then replace the above line with this one:

$GIT_PATH="/usr/local/bin";

See “support for git installed outside default PATH” in the Gitolite documentation.

Gitolite 3.x

The 3.x version of Gitolite is a complete rewrite. One of the incompatibilities with respect to the 2.x series is the lack of $GIT_PATH. From the “incompatible features”, “high impact” section of the migration documentation:

GIT_PATH dropped, requires presetting.

If you need its functionality, add these lines to the end of the rc file:
$ENV{PATH}="...whatever you want...";
1;

So, for Gitolite 3.x, the ~/.gitolite.rc change should be something like this:

$ENV{PATH}="/usr/local/bin:$ENV{PATH}";

(somewhere before the final 1; line)