Issue after vscode update to 1.36.0

[gmtechworks]

Error while connecting to SSH FS "connection name":
Error while signing data with privateKey: error:06000066:public key routines:OPENSSL_internal:DECODE_ERROR

[badcrc]

I'm getting an openssl error too after updating to 1.36.0:

Error while signing data with privateKey: error:06000080:public key routines:OPENSSL_internal:UNSUPPORTED_ALGORITHM

I've tried with a RSA and a DSA keys and both fails.

[sikmike]

I can confirm. I am getting the same error connecting to an AWS linux server:

Error while connecting to SSH FS mydev:
Error while signing data with privateKey: error:06000066:public key routines:OPENSSL_internal:DECODE_ERROR

[dolbyac3]

Upgraded to vscode 1.36 and get the following error:

Error while connecting to SSH FS web1:
Error while signing data with privateKey: error:06000066:public key routines:OPENSSL_internal:DECODE_ERROR

Reverted back to vscode 1.35.1 and everything works fine.

[jacobmata]

Same for me after upgrading VSCode
Error while connecting to SSH FS do2: Error while signing data with privateKey: error:06000066:public key routines:OPENSSL_internal:DECODE_ERROR

[rotexhawk]

Same issue on mac.

[SchoofsKelvin]

I'm not entirely sure what's going on. It seems like vscode upgraded Electron to 4.x, which uses a new SSL library that dropped support for some key types.

The weird thing is that RSA should still be supported, but @badcrc had an issue with that too?

Version changes:

• vscode 1.36 upgraded node 10.2.0 to 10.11.0
• node 10.9.0 updated OpenSSL from 1.1.0h to 1.1.0i
• upgraded to Electron 4
• Electron switched to BoringSSL (apparently overriding node's version)

Similar issues:

• Error while signing data with privateKey: error:06000066:public key routines:OPENSSL_internal:DECODE_ERROR liximomo/vscode-sftp#594
• crypto.createVerify('sha1').verify() failed in version 1.36.1 microsoft/vscode#77500
• Unknown ciphers: aes-256-cfb, aes-128-cfb electron/electron#16195 (actual cause)

[badcrc]

I've just tried with a rsa key and seems to work, maybe I didn't try it right the first time.

[SchoofsKelvin]

I'll keep this issue open for a while and keep looking around, but right now it seems like it's not something I can fix, without dynamically converting keys if that's even possible.

[dolbyac3]

I think it has to do with the key bit size length.

I was using some older rsa keys so I re-generated them with a bit size of 4096 (ssh-keygen -t rsa -b 4096) and they worked with this plugin running on vs code 1.37.1.

Then I generated some new keys with the default bit size (2048) and they did not work. Just to test that.

So if you are having trouble try generating a stronger rsa key.

[rotexhawk]

I am able to login to my remote servers after the recent VScode update. 1.37.1

[over-engineer]

@dolbyac3 Yes! Thank you! I was going crazy while trying to fix an issue on an Electron app for the past 3 hours. You really saved my bacon.

[Trimakas]

Shoot, still having this issue. tried PEM format and the 4096 length format, both with no luck.. anyone else still having this issue?

[jorgehumberto]

having the same issue here. I am on:

• Fedora 31 (64)
• vscode 1.40.2
• shfs 1.16.3

[SchoofsKelvin]

This should be fixed after updating ssh2 (b22dd71) and VSCode updating their node version.

[dylanh724]

Andd it's back: liximomo/vscode-sftp#830

[SchoofsKelvin]

The extension is already using [email protected] which in turn uses [email protected], both the latest versions.
Need to wait on ssh2 to complete its rewrite, or accept this PR: mscdex/ssh2-streams#164.