If you are using those tow accounts with different ssh keys (as described in "How do programs like gitolite work?"), the way you switch is by using an ssh url which instructs ssh to look for noah's key (instead of admin's key).
For that, you need an ssh config file (in your HOME/.ssh/config
), as I detailed in "How to use specified key when working with github via portablegit?":
#admin account
Host gitolite-admin
HostName yourGitoliteServer
User git
IdentityFile ~/.ssh/id_rsa_admin
#noah account
Host gitolite-noah
HostName yourGitoliteServer
User git
IdentityFile ~/.ssh/id_rsa_noah
To clone your repo made for noah, you would use an url which reference the right entry in the ssh config file.
git clone gitolite-noah:yourRepo.git
By using that url, you are setting a remote named origin
: you can see it with git remote -v
.
That means any command using that remote name (like git pull origin or git push origin) will use that ssh url, which explicitly refers to a specific private ssh key, which in turn identifies you to Gitolite as noah
.
The most effective way to debug ssh is by checking how the sshd listen to the query on the server.
Since it is a debian (as per out discussion):
/usr/sbin/sshd -d -D -p 222
on the server,
ssh -p 222 -Tv git-noah
on the client
(note the trick of using a dedicated port, that way, no need to stop the actual sshd: it is a one-time session on a special port for debug purpose only)
We quickly saw a
Could not open authorized keys '/home/git/.ssh/authorized_keys': Permission denied
Which is consistent with:
root@server:/# ls -lato ~git/
drw------- 2 git 4096 Apr 19 14:57 .ssh
A chmod 700 ~git/.ssh
fixed the situation.
Best Answer
Here's the workflow for adding users to gitolite:
Add the users public key to the map
keys
as<username>.pub
Edit your gitolite config file (
gitolite.conf
), this file is in the mapconf
. When you open it, everthing will be clear.example:
Commit the new key and the modified config file. Then push it to your gitolite server.
That should do it!
[Edit] BTW, here is the gitolite paragraph that explains what I wrote above: http://gitolite.com/gitolite/conf.html.