Problems using Tortoise SVN with SSH (Phabricator server).

782 views
Skip to first unread message

alastair...@yahoo.co.uk

unread,
Jul 11, 2018, 12:23:42 PM7/11/18
to torto...@googlegroups.com
I am trying to use TortoiseSVN with a Phabricator (https://www.phacility.com/) SVN server which insists on a SSH connection using public keys.

My TortoiseSVN version is 1.10.0, Build 28176 - 64 Bit , 2018/04/14 08:00:32 and "Check for Updates" tells me that this is the latest version.

I have set up a public key and so on and got the SVN connection working with a standard subversion command line client.

If on a command line I do:

    "C:\Program Files\TortoiseSVN\bin\TortoisePlink.exe" -i "mykey.ppk" -l svn -P 2222 phabricator.local.network svnserve

I get the response:

    ( success ( 2 2 ( ) ( edit-pipeline svndiff1 absent-entries commit-revprops depth log-revprops atomic-revprops partial-replay inherited-props ephemeral-txnprops file-revs-reverse ) ) )

which seems to me to be the correct response (based on previous experimentation during earlier debugging).

I then go to the TortoiseSVN settings and for the SSH client I enter:

    "C:\Program Files\TortoiseSVN\bin\TortoisePlink.exe" -i "mykey.ppk" -l svn -P 2222

I then use TortoiseSVN to browse the repository:

    svn+ssh://phabricator.local.network/source/trunk

and get messages like "Unable to connect to repository at that URL" and "Connection closed unexpectedly".

I am trying to figure out how to sniff the comms to see what is going wrong, but...it's SSH. Apparently "DebugView" (https://github.com/CobaltFusion/DebugViewPP) allows this but I am doubtful.



This looks like a bug to me. If I can get the Subversion server to talk to me properly using TortoisePlink, and I can browse the repository and perform other actions using a Subversion command line client, then TortoiseSVN should be able to work with this server.



Before anyone says "Well just use the command line client then", I'd like to point out that A) this should work and so needs to be fixed if broken, and B) I am more than happy to use the command line client, but my work colleagues, who I am trying to set this up for, most definitely are not.

Ulrike Löber

unread,
Jul 11, 2018, 12:26:58 PM7/11/18
to TortoiseSVN on behalf of Alastair Growcott
I posted a similar question a few days ago and still have neither an answer nor a solution yet. 

<tortoisesvn+APn2wQfC__Yvx_I43f4s...@googlegroups.com> schrieb am Mi., 11. Juli 2018, 18:23:
I am trying to use TortoiseSVN with a Phabricator (https://www.phacility.com/) which insists on a SSH connection.
--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/637a4bb1-9c60-46a5-81ea-dc71fd5a1d76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Stefan

unread,
Jul 11, 2018, 12:50:08 PM7/11/18
to TortoiseSVN
If you got it working with the command line client, then that means you have set up the [tunnels] section in the subversion config file already?
Because then you can just leave the TSVN setting for the SSH empty and it will use the config from svn.

Alastair Growcott

unread,
Jul 12, 2018, 2:39:28 AM7/12/18
to TortoiseSVN
I understood that the SVN config file didn''t get used, that only The TortoiseSVN config was used. I think I read that somewhere.

In any case, the command line client I was using was the MSys2 bash shell client and I didn't edit the SVN config file, just the $HOME/.ssh/config file.

For extra information:
  • I also set up a full putty session and used the name of it in the URL and got the same basic behaviour.
  • I tried using pageant and kept getting asked for a password.

Reply all
Reply to author
Forward
0 new messages