Does this work with svn+ssh/rsa (passphrase protected) + SSH-Remote

[ghostkadost]

• VS Code Version: 1.44.1
• OS: Darwin x64 19.4.0
• Remote host : Linux
• svn, version 1.10.2 (r1835932)
• Remote-ssh : 0.51.0
• svn extension 2.10.6
• svn gutter 0.5.2

Issue
I use svn+ssh with rsa keys protected with a passphrase.

Unable to do a diff between head and local, unable to view file history, commit, etc. The only operation that works is "show all diff patches"

This is how the file diff looks like. I have masked the actual contents of the file.

This is how svn file history and repository status looks like. I have only masked the repo name and file name.

I am running ssh-agent on the remote host and appropriate keys are added. I am able to perform all svn operations from the integrated terminal and can verify that the ssh-agent related environment is properly set up

Similarly, the SVN gutter extension throws the following error while executing "show blame"

svn: E170013: Unable to connect to a repository at URL 'svn+ssh://svn@' svn: E210002: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. svn: E210002: Network connection closed unexpectedly

Here is the .ssh/config file section for connecting to svn

Host *-svn-0*
User svn
IdentityFile /homes/user-name/.ssh/id_rsa

[JohnstonCode]

Do you get any errors in the SVN extension output when you try running on of the failed commands?

[ghostkadost]

How do we check the extension output?

[JohnstonCode]

View >> Output then select svn

[ghostkadost]

Yeah got that. This on triggering diff between HEAD and local.

[work]$ svn info --xml
[work]$ svn cat -r HEAD svn+ssh://svn@"file_path"
[work]$ svn: E170013: Unable to connect to a repository at URL 'svn+ssh://svn@fie_path'
[work]$ svn: E210002: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
[work]$ svn: E210002: Network connection closed unexpectedly[work]$ svn info --xml full_path_of_file

[JohnstonCode]

If you copy and paste the svn cat line and run it in the terminal does it work?

[ghostkadost]

Yes. The contents of the file are displayed if I run this from the integrated terminal.

[JohnstonCode]

Do you get a prompt for the ssh passphrase?

[ghostkadost]

No. As I mentioned ssh-agent takes care of that.

[JohnstonCode]

Okay I've not had this issue before using svn+ssh I will try to reproduce however.

[ghostkadost]

Is there a way to remove the -q option as suggested in the error message?

[JohnstonCode]

I'm not sure never had to do it before

[JohnstonCode]

Not able to replicate.

[ghostkadost]

I figured out how to enable verbose logging for tunnels in svn. Here is what I see
[work]$ debug1: Offering RSA public key: /homes/user_name/.ssh/id_rsa
[work]$ debug3: send_pubkey_test
[work]$ debug3: send packet: type 50
[work]$ debug2: we sent a publickey packet, wait for reply
[work]$ debug3: receive packet: type 60
[work]$ debug1: Server accepts key: pkalg rsa-sha2-512 blen 277
[work]$ debug2: input_userauth_pk_ok: fp ---------------------------
[work]$ debug3: sign_and_send_pubkey: RSA ------------------------
[work]$ debug1: read_passphrase: can't open /dev/tty: No such device or address
[work]$ debug2: no passphrase given, try next key
[work]$ debug2: we did not send a packet, disable method
[work]$ debug3: authmethod_lookup password
[work]$ debug3: remaining preferred: ,password

Is there a way to setup the connection with ssh-agent like the integrated terminal or prompt for pass phrase?

[JohnstonCode]

Not for ssh there isn't.

[ghostkadost]

My apologies if I am dragging this. The Remote-SSH extension can prompt for pass-phrase. Can something be borrowed from there?

[JohnstonCode]

I don't think so as they are using ssh directly whereas this extension is using svn i cant catch anything as it has already failed.

[JohnstonCode]

If the ssh agent is running you shouldn't need to enter a password

[ghostkadost]

From the integrated shell

[work]$ echo $SSH_AGENT_PID
255
[work]$ ps ux | grep ssh-agent
user 255 0.0 0.0 11144 308 ? Ss Apr06 0:00 ssh-agent
[work]$ echo $SSH_AUTH_SOCK
/tmp/ssh-8vt0fQEukMtJ/agent.254

Thanks for patiently answering my queries.

[JohnstonCode]

i do get something different if i do ps ux | grep ssh-agent it lists my keyring
/usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh

[JohnstonCode]

Not sure how keyring and ssh work on Mac

[ghostkadost]

Your comment on ssh-agent made me wonder if there is something wrong in my environment. Played around with the setting of SSH_AUTH_SOCK and happy to report that everything now works link a charm.

Thanks a lot.

[JohnstonCode]

Glad to hear that you managed to get it working.

[wwiki]

I got the same issue after updated to macOS 10.15.4 😭
Fixed by pasting in Terminal: ssh-add -K ~/.ssh/id_rsa
Works now.
Thanks for the great extension Christopher!!