On Thu, Jul 19, 2012 at 10:26 AM, mart <martve...@gmail.com> wrote: > > >> While searching for similar problem, I found people saying it was related >> to the ssh key. I don't know if it is the problem but "$ ssh >> g...@git.server.com" works fine on me. I have put the public key in >> /etc/ssh/keys/git/autorized_**keys (I don't have a home folder for the >> git user) and imported the same in the gitorious interface for my user. >> >> Any idea what can cause the problem ? >> >> > Ok I posted too fast. It seems it was indeed a ssh key problem. Gitorious > created a file in the gitorious folder .ssh/autorized_keys with the > following > > ### START KEY 2 ### > command="gitorious > mart",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty > ssh-rsa AAAAB3...gs9c9 SshKey:2-User:1 > ### END KEY 2 ### > > Putting that key in the /etc/ssh/keys/git/autorized_keys instead allowed > me to connect and do push >
The authorized_keys file is populated by the poller script, which in turn will use $HOME/.ssh/authorized_keys for saving these files. Had your authorized_keys file been in /etc/.ssh you should get by with running the poller like this `HOME=/etc script/poller run`, but in your case you should be able to get by with symlinking the files to their proper location instead. Cheers, - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
