Permission denied (publickey) On second Step ... ?

Hello,

I've a strange (for me ;-)) problem.
I'm trying to use git-annex with 2 debian wheezy (packages from backports)
I've put my ssh pub key on the server in the autorized_keys for my username account (and for the root account to be sure) my username account is member of the sudo group (not sure it's required)

I can create an ssh session directly to the server with :

ssh username@remoteserver.lan -p 62322

and work inside this session.

Sep 14 03:42:35 file sshd[8849]: Accepted publickey for username from 80.201.25.4 port 32969 ssh2
Sep 14 03:42:35 file sshd[8849]: pam_unix(sshd:session): session opened for user username by (uid=0)
...
Sep 14 05:13:14 file sshd[8851]: Received disconnect from 80.201.25.4: 11: disconnected by user
Sep 14 05:13:14 file sshd[8849]: pam_unix(sshd:session): session closed for user username

But when I use the git-annex assistant on the same workstation with the same remote server and port,
the 1st step is OK,
but when I've to choose between git or rsync encrypted, I'm choosing git and receive :

"Permission denied (publickey)."

On the server I can only see that the ssh session is immediately closed after opened and before the choice git or rsync is made.

Sep 14 05:13:42 file sshd[8882]: Accepted publickey for username from 80.201.25.4 port 32984 ssh2
Sep 14 05:13:42 file sshd[8882]: pam_unix(sshd:session): session opened for user username by (uid=0)
Sep 14 05:13:42 file sshd[8886]: Received disconnect from 80.201.25.4: 11: disconnected by user
Sep 14 05:13:42 file sshd[8882]: pam_unix(sshd:session): session closed for user username

Do you think it's the problem ? or whatelse ...
and could you guide me to a possible solution ?

Best regards

RSS Atom

comment 1

The webapp sets up a dedicated ssh public key when you add a ssh repository in there.

You might see some useful debugging info your your problem in ~/annex/.git/annex/daemon.log

Comment by joeyh.name — Fri Nov 8 18:24:27 2013

Remove comment

OK,thanx for this

The problem is not solve, but with your informations, I think i've found somehting.

Is it possible that the problem is linked to my situation of port-forwarding ? The remoteserver is a host (proxmox) with iptable port forwarding 62322 to the real port 22 of the VM hosting the git where I try to connect.

So could the problem seems to be that some actions are taken on the host and not the VM ... correct ?

[2013-11-09 09:51:33 CET] read: ssh-keygen ["-F","bla.remote.tld"]
[2013-11-09 09:51:33 CET] read: ssh ["-oNumberOfPasswordPrompts=0","-n","-p","62322","user@bla.remote.tld","sh -c 'echo git-annex-probe loggedin;if which git-annex-shell; then echo git-annex-probe git-annex-shell; fi;if which rsync; then echo git-annex-probe rsync; fi;if which ~/.ssh/git-annex-shell; then echo git-annex-probe ~/.ssh/git-annex-shell; fi'"]
[2013-11-09 09:51:35 CET] chat: ssh ["user@bla.remote.tld","sh -c 'mkdir -p '\"'\"'annex'\"'\"'&&cd '\"'\"'annex'\"'\"'&&if [ ! -d .git ]; then git init --bare --shared; fi&&git annex init'"]

If it's correct, have you an idea for solving this ?

best regards

Comment by Auroch — Sat Nov 9 09:10:42 2013

Remove comment

comment 3

Well, it does look like your git-annex did not pass the port to the second command.

What version are you using? I've just tested with a ssh server only listening on 2222 and it used the port throughout.

You might try upgrading to a recent version. I know that version 4.20130627, at least, had a bug with the ssh port.

Comment by joeyh.name — Sat Nov 9 18:07:56 2013

Remove comment

comment 4

I've the wheezy-backports version

i   4.20131002~bpo70+1                                                        wheezy-backports                                      100