Last VSCode 1.82 = issue with VMS-IDE 1.5.55
-
Topic author - Valued Contributor
- Posts: 51
- Joined: Thu Jul 18, 2019 8:18 am
- Reputation: 0
- Status: Offline
Last VSCode 1.82 = issue with VMS-IDE 1.5.55
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
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
Last edited by l.cedric on Mon Sep 11, 2023 4:55 am, edited 1 time in total.
-
- VSI Expert
- Master
- Posts: 103
- Joined: Thu Aug 22, 2019 12:17 am
- Reputation: 0
- Status: Offline
Re: Last VSCode 1.82 = issue with VMS-IDE 1.5.55
The new version of VMS-IDE has released.
This issue must be fixed, I hope.
This issue must be fixed, I hope.
-
Topic author - Valued Contributor
- Posts: 51
- Joined: Thu Jul 18, 2019 8:18 am
- Reputation: 0
- Status: Offline
Re: Last VSCode 1.82 = issue with VMS-IDE 1.5.55
Thanks Sergey,
I just tested, and I have now this old issue :
So I guess this new issue is due to what I've read in your 1.5.58 release notes :
EDIT:
If needed the OpenVMS SSH server log
I just tested, and I have now this old issue :
- "client error: Error: Handshake failed: signature verification failed"
So I guess this new issue is due to what I've read in your 1.5.58 release notes :
- "The 'skipSignatureVerification' SSH connection option is no longer used"
- skipSignatureVerification - Skip signature verification. Set it to 'true' if an error 'Handshake failed: signature verification failed' occurs.
EDIT:
If needed the OpenVMS SSH server log
Last edited by l.cedric on Fri Sep 29, 2023 9:02 am, edited 2 times in total.
Re: Last VSCode 1.82 = issue with VMS-IDE 1.5.55
Hi Alister! It's always dependent on the question, and the best way to know the answer is to make a request to the Support team. Generally, if it's in the list of Products on the website, it's supported. But:
- There are some outliers, such as some old HPE products which might be mentioned, but we don't/can't/won't maintain them. So it's better to ask and we'll return with an official answer
- There are cases where the product is in scope, but your question is not, like "Please, edit my data for me", and the Support will notify you if that's the case as well.
So please write them, so you will know the exact answer. And the request itself will be properly tracked, won't be lost, etc. The forum is a good place to find or share the information, but still not an "official" channel (I've read some heated topics on that subject already, so I wanted to mention that once again).
I'm new to the company, I joined a few months ago as a Product Manager, and this is my first comment there actually. So be gentle guys, don't kill me right away
Nikita
Re: Last VSCode 1.82 = issue with VMS-IDE 1.5.55
Hi.
I would just like to add that, even if an issue moves over to official support channels, it is still nice with a follow up here in the forum, for us that has already read about It...
I would just like to add that, even if an issue moves over to official support channels, it is still nice with a follow up here in the forum, for us that has already read about It...
Last edited by sodjan on Sat Sep 30, 2023 5:40 pm, edited 1 time in total.
Re: Last VSCode 1.82 = issue with VMS-IDE 1.5.55
Right... My spelling checker thinks I'm writing everything in Swedish...
-
- VSI Expert
- Master
- Posts: 103
- Joined: Thu Aug 22, 2019 12:17 am
- Reputation: 0
- Status: Offline
Re: Last VSCode 1.82 = issue with VMS-IDE 1.5.55
The option skipSignatureVerification was added in our own branch of SSH2 project. SSH2 project has moved forward. We need a time to implement skipSignatureVerification feature in the current version of the SSH2 project.
-
Topic author - Valued Contributor
- Posts: 51
- Joined: Thu Jul 18, 2019 8:18 am
- Reputation: 0
- Status: Offline
Re: Last VSCode 1.82 = issue with VMS-IDE 1.5.55
Thank Sergey
In the meantime our team must remain in VSCode 1.81 and VMS-IDE 1.5.55
Added in 6 hours 3 minutes 6 seconds:
Hi Sergey,
I'm fight against the PM system
So I don't know if you received my answer to your pm (?). It is still in the Outbox and I don't know how to sent it ...
(Not yet in the "Sent messages" box !?)
In the meantime our team must remain in VSCode 1.81 and VMS-IDE 1.5.55
Added in 6 hours 3 minutes 6 seconds:
Hi Sergey,
I'm fight against the PM system
So I don't know if you received my answer to your pm (?). It is still in the Outbox and I don't know how to sent it ...
(Not yet in the "Sent messages" box !?)
Last edited by l.cedric on Mon Oct 02, 2023 9:09 am, edited 2 times in total.
-
- VSI Expert
- Master
- Posts: 103
- Joined: Thu Aug 22, 2019 12:17 am
- Reputation: 0
- Status: Offline
Re: Last VSCode 1.82 = issue with VMS-IDE 1.5.55
OK. Tomorrow we will release 1.5.59 for all.
Re: Last VSCode 1.82 = issue with VMS-IDE 1.5.55
Hi Sergey and Toofpic (?),
Thank you for the prompt responses. Firstly I hope my enquiry about VMS IDE being supported or not wasn't misinterpreted - i wasn't expecting a same day response ! I will post a support request as per your suggestion to know for sure about VMS IDE's status. The backstory is that we have a team that's relatively "split" - those that know and can edit the VMS code and those that work on newer systems and struggle to upskill with VMS. I see VMS IDE as being a real possibility to shrink that gap - but it would become critical to those peoples workflows, so i want to make sure that there are resources around to keep it reliable.
I am also using the skipSignatureVerification so i'll wait for tomorrows release. Todays release has re-asserted that error for me. Though i'm at pains to point out that these are obviously two or three different errors - one around kex exchange, one around signature verification, and another which i posted about around sftp operations failing - with quite different causes i imagine.
I note from the release notes that the default kex algorithms and signatures were removed. An idea - It would be great at the end of this if we could update the wiki somewhat around what VMS ide is doing in various actions e.g during a sync it establishes an ssh connection using (ssh2-stream), does a directory listing using sftp, then creates a root directory if required (??). I've had to infer this from a combination of the developer tools, reading the code and wireshark debugging. Because VMS systems are typically older, AND failing to make and ssh connection makes this extensions usage fail at the first hurdle, a bit more hand holding of users might help. Not a gripe, just trying to provide some constructive comments !
Thank you for the prompt responses. Firstly I hope my enquiry about VMS IDE being supported or not wasn't misinterpreted - i wasn't expecting a same day response ! I will post a support request as per your suggestion to know for sure about VMS IDE's status. The backstory is that we have a team that's relatively "split" - those that know and can edit the VMS code and those that work on newer systems and struggle to upskill with VMS. I see VMS IDE as being a real possibility to shrink that gap - but it would become critical to those peoples workflows, so i want to make sure that there are resources around to keep it reliable.
I am also using the skipSignatureVerification so i'll wait for tomorrows release. Todays release has re-asserted that error for me. Though i'm at pains to point out that these are obviously two or three different errors - one around kex exchange, one around signature verification, and another which i posted about around sftp operations failing - with quite different causes i imagine.
I note from the release notes that the default kex algorithms and signatures were removed. An idea - It would be great at the end of this if we could update the wiki somewhat around what VMS ide is doing in various actions e.g during a sync it establishes an ssh connection using (ssh2-stream), does a directory listing using sftp, then creates a root directory if required (??). I've had to infer this from a combination of the developer tools, reading the code and wireshark debugging. Because VMS systems are typically older, AND failing to make and ssh connection makes this extensions usage fail at the first hurdle, a bit more hand holding of users might help. Not a gripe, just trying to provide some constructive comments !