Date: Wed, 20 Apr 2011 16:41:15 -0400 From: Greg Larkin <glarkin@FreeBSD.org> To: =?ISO-8859-15?Q?Michael_Gr=FCnewald?= <michaelgrunewald@yahoo.fr> Cc: FreeBSD questions <freebsd-questions@freebsd.org> Subject: Re: Subversion over SSH works through GIT but not with SVN Message-ID: <4DAF44EB.90002@FreeBSD.org> In-Reply-To: <4DAEC1A3.8070305@yahoo.fr> References: <4DAEC1A3.8070305@yahoo.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/20/11 7:21 AM, Michael Gr=FCnewald wrote: > Hi all, >=20 > I have recently discovered that by subversion client (1.16_2) is not > able any more to access my subversion accounts over svn+ssh (with key > based authentication). It seems very odd to me, because in the same > time git can access these accounts (with the git svn command) and commi= t > to these repositories! >=20 > I am here absolutely clueless, so I would welcome your insights and you= r > help! >=20 > I set up `SVN_SSH' to `ssh -vv' in order to get a little more feedback > than the `connexion unexpectedly closed' that subversion gave me. Here > is an exceirpt of the successful svn+ssh authentication achieved by git > svn: >=20 > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug2: key: /home/michael/.ssh/id_rsa (0x801a61680) > debug2: key: /home/michael/.ssh/id_dsa (0x0) > debug1: Authentications that can continue: publickey > debug1: Next authentication method: publickey > debug1: Offering public key: /home/michael/.ssh/id_rsa > debug2: we sent a publickey packet, wait for reply > debug1: Server accepts key: pkalg ssh-rsa blen 277 >=20 > on the pure svn side I have instead >=20 > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug2: key: /home/michael/.ssh/id_rsa (0x801a61660) > debug2: key: /home/michael/.ssh/id_dsa (0x0) > debug1: Authentications that can continue: publickey > debug1: Next authentication method: publickey > debug1: Offering public key: /home/michael/.ssh/id_rsa > debug2: we sent a publickey packet, wait for reply > debug1: Authentications that can continue: publickey > debug1: Trying private key: /home/michael/.ssh/id_dsa > debug2: we did not send a packet, disable method >=20 > (this is the point were the two transcripts start to disagree). I do > not know what is the hex value after the name of the file containing my > private key, but it semms weird to me that the two runs give here > different results! Do you see a symptom related to my problem? Hi Michael, I think the hex value discrepancy is significant, but I'm not yet sure why the value changes. The private key filename looks the same. When I run into problems like this, I first start by eliminating the application connecting through ssh and just try a standard ssh connection like so: ssh -vvv -l <username> <hostname> You may also want to add "-i ~/.ssh/id_rsa" to the command line to see if that changes anything. If you authenticate successfully with that command, then check the ~/.subversion/config file for suspect entries in the [tunnels] section. Finally, if all else fails, I run commands through truss or strace to see if there are any strange errors generated by system calls, like a missing library or config file, or an unexpected chdir() or chroot(). Hope that helps, Greg - --=20 Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2vROsACgkQ0sRouByUApDzZwCfaQ1TPWXr4YFNKRhE792XXR3o LBMAnjWrw8Y+DqZnAz9YJqP/Qh9lS7uX =3DwtcF -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DAF44EB.90002>