VSCode and SSH FS are not making a connection to a remote host
by rnturn from LinuxQuestions.org on (#5RW2X)
This one's sort of got me scratching my head.
I have VSCode installed on Leap (15.3) and I've installed the SSH FS extension in an attempt to set up a connection to a directory tree on a Slackware system.
I have SSH keys set up that allow me to connect from Leap to Slackware (and vice versa) passwordlessly; I've been doing this without problems for a long time. However when I create a connection configuration pointing to a file tree on the Slackware system and attempt to connect to it, I receive an error stating that my key is not valid:
Code:Error while connecting to SSH FS my_remote_connection_name:
privateKey value does not contain a (valid) private keywhich doesn't make sense to me as I can connect via ssh from a bash prompt without any errors.
I get a similar error message about an invalid private key if I attempt to open a terminal to the Slackware system from within VSCode.
So...
I tried setting up the connection with a password. This is not the way I wanted to go since VSCode tells you that the password is saved in plaintext. But... it worked and I was able to connect though not using a secure method if the password is, indeed, stored as plaintext somewhere. (I grepped for the remote account's password within everything under $HOME/.vscode and was not able to find any files. It does, however, appear in plaintext in files under $HOME/Code. [ugh])
I suspect the errors I'm seeing have got something to do with some arcane aspect of how I should configure the remote connection but, frankly, the configuration screen/form looks logical enough. Apparently I'm missing something subtle (or maybe the extension didn't actually install properly).
Q1: Any ideas on what would cause VSCode + SSH FS to believe that my SSH key is invalid?
Q2: Could it be that the keys are actually not compatible with SSH FS? I haven't found anything that stated that I needed to create keys in a particular way that will play nice with this extension and it wouldn't be too awful to have to generate new keys if that's actually needed.
TIA... for any information about this.
I have VSCode installed on Leap (15.3) and I've installed the SSH FS extension in an attempt to set up a connection to a directory tree on a Slackware system.
I have SSH keys set up that allow me to connect from Leap to Slackware (and vice versa) passwordlessly; I've been doing this without problems for a long time. However when I create a connection configuration pointing to a file tree on the Slackware system and attempt to connect to it, I receive an error stating that my key is not valid:
Code:Error while connecting to SSH FS my_remote_connection_name:
privateKey value does not contain a (valid) private keywhich doesn't make sense to me as I can connect via ssh from a bash prompt without any errors.
I get a similar error message about an invalid private key if I attempt to open a terminal to the Slackware system from within VSCode.
So...
I tried setting up the connection with a password. This is not the way I wanted to go since VSCode tells you that the password is saved in plaintext. But... it worked and I was able to connect though not using a secure method if the password is, indeed, stored as plaintext somewhere. (I grepped for the remote account's password within everything under $HOME/.vscode and was not able to find any files. It does, however, appear in plaintext in files under $HOME/Code. [ugh])
I suspect the errors I'm seeing have got something to do with some arcane aspect of how I should configure the remote connection but, frankly, the configuration screen/form looks logical enough. Apparently I'm missing something subtle (or maybe the extension didn't actually install properly).
Q1: Any ideas on what would cause VSCode + SSH FS to believe that my SSH key is invalid?
Q2: Could it be that the keys are actually not compatible with SSH FS? I haven't found anything that stated that I needed to create keys in a particular way that will play nice with this extension and it wouldn't be too awful to have to generate new keys if that's actually needed.
TIA... for any information about this.