Last VSCode 1.82 = issue with VMS-IDE 1.5.55

[l.cedric]

Hello,

last week our teams had to reinstall the previous VSCode 1.81.1
instead of the last one 1.82

The issue for Quick Upload or Upload was :

(The full upload tip given in the error message does not help => same issue)

Thanks in advance

[sergey_vorfolomeev]

• Enable log: in the VMS-IDE settings fill in the Debug output, 'console' or folder field.

• Allow 'debug' for connection: in the ssh settings set 'debug': true for the desired host.

• Analyze log file

Seems like connection string has the invalid diffie-hellman group (or does not have it valid).
https://www.watchguard.com/help/docs/he ... man_c.html

https://wiki.vmssoftware.com/SSH_Settings

[jeremybegg]

Hi,

After trying and failing to set up VS Code with the VMS IDE a couple of years ago, I thought I'd try again - and immediately hit the problem reported in this thread.

My OpenVMS IA64 server is running MultiNet 5.6 and after discussion with Process Software via the info-multiinet mailing list I came up with this addition to the vmssoftware.ssh-helper-setting.json file:

Code: Select all

        "algorithms": {
            "kex": [
                "diffie-hellman-group14-sha1",
                "diffie-hellman-group14-sha256"
            ],
            "cipher": [
                "aes128-cbc",
                "3des-cbc"
            ],
            "serverHostKey": [
                "ssh-rsa",
                "ssh-dss",
                "ecdsa-sha2-nistp256",
                "ssh-ed25519"
            ]
        },

MultiNet tends to settle on "diffie-hellman-group1-sha1" by default but that's what the IDE is complaining about. If I'm reading MiultiNet's log correctly, the IDE was happy with "diffie-hellman-group14-sha1".

Unfortunately the transfer failed, with VSI IDE reporting: "donwload failed:" followed by a filename. The file in question is a Pascal source file in StmLF format. It must have successfully retrieved a directory listing (in some form) from VMS because the file does not currently exist locally.

I don't see a client-side log anywhere to help debug this.

Regards,

Jeremy Begg

[l.cedric]

Hi Sergey,

Tried to do what you asked (but just two more lines ...)

And according to Jeremy answer, i've tried to change the DH group, but without success about VSCode & VMS-IDE
(before it was 'diffie-hellman-group1-sha1')

Code: Select all

C:\Users\xxxxxxx>ssh -V
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2

C:\Users\xxxxxxx>type c:\Users\xxxxxxx\.ssh\config
HostKeyAlgorithms +ssh-dss
KexAlgorithms +diffie-hellman-group14-sha256
C:\Users\xxxxxxx>
C:\Users\xxxxxxx>ssh user@server dir

Directory DISK$HOME:[users.user]
AIR_STOP_USER_BD.COM;6                  ALPEX1_TRACE.DSC;1  announce.txt;9
build_or_deploy_kit_git.com;1           curl.DIR;1
etc...

Regards

[sergey_vorfolomeev]

Hi

The issue is the latest version of VS Code does not support diffie-hellman-group-sha1 and -sha2
See https://github.com/electron/electron/issues/39603

The solution is to downgrade of VS Code.

[spoofy]

To which version we need to downgrade VSCode?

[sergey_vorfolomeev]

I have VS Code 1.81.1 with Node.js 16.14.7 and all works.

[l.cedric]

Hi

The issue is the latest version of VS Code does not support diffie-hellman-group-sha1 and -sha2
See https://github.com/electron/electron/issues/39603

The solution is to downgrade of VS Code.

Thank you very much for your response Sergei
I now need to ask our OpenVMS IT teams to upgrade our OpenVMS SSH service to be able to use a supported algorithm (necessarily more secure )
Regards

[l.cedric]

The solution is to downgrade of VS Code.

Hi Sergey,
Is this currently the only solution?


After reading the issues you indicated and seeing that only a few key types (diffie-hellman) were affected , I was hoping to change the key in the Windows10 client c:\users\xxxxxx\.shh\config with one of the first two:

Code: Select all

debug2: peer server KEXINIT proposal
debug2: KEX algorithms: diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

(given from my Windows10 by an ssh -vvv ...)

Without KexAlgorithms in the config file, it chooses on its own :

Code: Select all

debug1: kex: algorithm: diffie-hellman-group14-sha256

with is not the diffie-hellman-group1-sha1, so it should work ...
In fact, they all work with this simple command ssh user@server_vms dir
but none with the VSCode (1.82) and VMS-IDE (1.5.55) Quick upload ...

Should we upgrade our SSH service on OpenVMS, to get more key types

Regards

Added in 3 hours 15 minutes 15 seconds:
Hi again,

I add this test if it helps (thanks to the above Jeremy post) :

Like him, I tried to force the algorithm like this (values were extracted from my Windows10 "ssh -v user@server_vms dir")

Code: Select all

        "algorithms": {
            "kex": ["diffie-hellman-group14-sha256"],
            "cipher": ["aes128-ctr"],            
            "serverHostKey": ["ssh-dss"],
            "hmac": ["hmac-sha1"],
            "compress": ["none"]            
        }

As Jeremy, no more the "Unknown DH group" error message,
but nevertheless a failed one

Code: Select all

upload failed: src/server/outi/environ_neo.com
Quick uploading failed. Please execute full synchronization or uploading.
Quick upload failed. [mantis]

[alister]

I believe i am also experiencing the same issue. The most relevant points are
- When performing a sync or upload i correctly see it determine what files are on or missing from the remote directory
- These operations succeed when there are no files to sync - empty project and/or empty remote directory
- Debug logging is enable, i only see "Upload failed" or "download failed"
- A node script i've written using ssh2-sftp CAN write a file successfully to the remote directory. The resulting file is streamlf format.
- Downgrading to 1.81 VSCode resolved the issue, (from 1.82)
- My enterprise forces regular upgrades so it's difficult to exist on previous versions
- Client side is Windows
- See attached screenshot for dev console logging
- I believe https://github.com/vmssoftware/vms-ide/ ... er.ts#L575 is where these log lines are generated
- Looking through the source, maybe https://github.com/vmssoftware/vms-ide/ ... am/pipe.ts is where it's failing, but i don't see any logging from that file present in my console output. Maybe i don't have debug logging correctly configured ?

Less relevant points
- I previously experienced issues establishing an ssh connection due to an older ssh stack on the VMS side. This was resolved by upgrading that, and forcing the key exchange algorithm - so i am confident that it is now not algorithm related
- Both the node script and VMS ide fail to create directories if they are missing, however both the node script and VSCode 1.81 succeed when the directory is present, so i don't believe this is relevant.

My company has a paid support contract with VSI. Is this considered a supported product ?