Re: svn+ssh on mingw32?

[Richard Frith-Macdonald]

On 8 Feb 2006, at 09:53, Sheldon Gill wrote:

> Richard Frith-Macdonald wrote:
> > Has anyone managed to get svn+ssh working on windowing in the  
> > ming32 environment yet?
>
> Well, I have. At least, I've fetched the code without issue over  
> ssh using my key.

Good to hear that it *can* work.

> > After installing svn-win32-1.3.0 to use from the msys command line  
> > I get 'svn: Connection closed unexpectedly'
> >
> > My ssh setup works fine for me normally (I was using it to access  
> > the CVS repository without trouble).
> >
> > I have tried adding an ssh key without password protection so that I
> > know that svn won't be confused by ssh wanting a password.
> > I have told ssh what username to use when contacting gna.org.
> >
> > My ssh config file says -
> >
> > Protocol 2
> > Host svn.gna.org
> > User rfm
> > IdentityFile ~/.ssh/insecure
> >
>
> I'd suggest you check it. Specifically with the gna server. Like this:
>
> ssh -l rfm svn.gna.org

As I said ... the ssh connection works fine.
In more detail, it says -

  Error:

  You are not allowed to run the command you asked.

  Only svn over ssh is accepted.  Please double-check the
  command line you typed.

and so on ... which proves that the ssh connection was established.

> > Any ideas?  It would be a pity if the move to subversion means we  
> > stop doing windows development.
>
> It would seem to me that the problem is your ssh session isn't  
> being established with the right credentials or that the key isn't  
> registered. The "Connection closed unexpectedly" message is the  
> tunnel being closed prematurely.

I expect so ... but the question is ... why?
My ssh connection works fine.
svn+ssh works fine on linux.
So the issue must be something to do with the subversion client ...  
my guess is it's not picking up the ssh configuration from ~/.ssh for  
some reason, but I haven't figured out how/why that can be the case.   
I also don't see how a problem with the command-line client could  
also effect the TortoiseSVN stuff ... which I configured completely  
independently using Putty stuff rather than OpenSSH stuff.  That's  
two different ssh implementations being used and both giving the same  
error.