Using TortoisePlink instead of SSH

[alanmcd]

I have always used the SVN command line to update, checkout etc in
conjunction with SSH and private key .ssh/id_dsa
(of course, I use tortoise as well)
This has worked fine for years now but with VISTA, I cannot make the
ssh connection (I get xmalloc errors or "key too open" errors
depending on the openssh version).
But the tortoiseSVN update works fine manually.

Maybe I don't understand something correctly, but is there a way to
make the svn.exe command line use the tortoiseplink connection instead
of the ssh connection?
I can load pageant with the key and tortoiseplink works fine without
password logon.

[my repos are all svn+ssh, and as I say tortoise works great with or
without pageant running with my key]

I've searched the archives here but I can't quite see if this issue is
discussed or if I'm asking the wrong question.

thanks Alan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-un...@tortoisesvn.tigris.org
For additional commands, e-mail: users...@tortoisesvn.tigris.org

[Milen A. Radev]

2008/9/22 alanmcd <al...@meta.com.au>:

> I have always used the SVN command line to update, checkout etc in
> conjunction with SSH and private key .ssh/id_dsa
> (of course, I use tortoise as well)
> This has worked fine for years now but with VISTA, I cannot make the
> ssh connection (I get xmalloc errors or "key too open" errors
> depending on the openssh version).
> But the tortoiseSVN update works fine manually.
>
> Maybe I don't understand something correctly, but is there a way to
> make the svn.exe command line use the tortoiseplink connection instead
> of the ssh connection?
> I can load pageant with the key and tortoiseplink works fine without
> password logon.
>
> [my repos are all svn+ssh, and as I say tortoise works great with or
> without pageant running with my key]
>
> I've searched the archives here but I can't quite see if this issue is
> discussed or if I'm asking the wrong question.
>

If you're trying to use the CLI client, plain plink.exe (from the
PuTTY installation) probably is a better choice.
Have you tried to change the "ssh=" line in your Subversion
configuration file (%APPDATA%\Subversion\config) to something like:

ssh=c:/path/to/plink.exe -i c:/path/to/your/key.ppk

That should go in the "[tunnels]" section of the file.

--
Milen A. Radev

[alanmcd]

> > I have always used the SVN command line to update, checkout etc in
> > conjunction with SSH and private key .ssh/id_dsa
> > (of course, I use tortoise as well)
> > This has worked fine for years now but with VISTA, I cannot make the
> > ssh connection (I get xmalloc errors or "key too open" errors
> > depending on the openssh version).
> > But the tortoiseSVN update works fine manually.
>
> > Maybe I don't understand something correctly, but is there a way to
> > make the svn.exe command line use the tortoiseplink connection instead
> > of the ssh connection?
> > I can load pageant with the key and tortoiseplink works fine without
> > password logon.
>
> > [my repos are all svn+ssh, and as I say tortoise works great with or
> > without pageant running with my key]
>
> > I've searched the archives here but I can't quite see if this issue is
> > discussed or if I'm asking the wrong question.
>
> If you're trying to use the CLI client, plain plink.exe (from the
> PuTTY installation) probably is a better choice.
> Have you tried to change the "ssh=" line in your Subversion
> configuration file (%APPDATA%\Subversion\config) to something like:
>
> ssh=c:/path/to/plink.exe -i c:/path/to/your/key.ppk
>
> That should go in the "[tunnels]" section of the file.
>
> --
> Milen A. Radev
>

Thanks - I've tried that too and while
"C:\Program Files\putty\plink.exe" user@host -i "C:\Users\Administrator
\.ssh\myprivate.ppk"
works fine.. when I edit the config with the same line (ex the
user@host) I get
svn: Commit failed (details follow):
svn: Can't create tunnel: The system cannot find the file specified.
back from SVN

I must be missing something else
Alan

[alanmcd]

> > I have always used the SVN command line to update, checkout etc in
> > conjunction with SSH and private key .ssh/id_dsa
> > (of course, I use tortoise as well)
> > This has worked fine for years now but with VISTA, I cannot make the
> > ssh connection (I get xmalloc errors or "key too open" errors
> > depending on the openssh version).
> > But the tortoiseSVN update works fine manually.
>
> > Maybe I don't understand something correctly, but is there a way to
> > make the svn.exe command line use the tortoiseplink connection instead
> > of the ssh connection?
> > I can load pageant with the key and tortoiseplink works fine without
> > password logon.
>
> > [my repos are all svn+ssh, and as I say tortoise works great with or
> > without pageant running with my key]
>
> > I've searched the archives here but I can't quite see if this issue is
> > discussed or if I'm asking the wrong question.
>
> If you're trying to use the CLI client, plain plink.exe (from the
> PuTTY installation) probably is a better choice.
> Have you tried to change the "ssh=" line in your Subversion
> configuration file (%APPDATA%\Subversion\config) to something like:
>
> ssh=c:/path/to/plink.exe -i c:/path/to/your/key.ppk
>
> That should go in the "[tunnels]" section of the file.
>
> --
> Milen A. Radev

sorry - works fine - just got the slashes wrong (again doh)
Alan