[Info-vax] SSH from VMS to 3Par

[Chris Townley]

On 06/10/2021 17:26, Stephen Hoffman wrote:
> On 2021-10-06 16:13:02 +0000, pcoviello at gmail.com said:
> 
>> On Wednesday, October 6, 2021 at 11:12:30 AM UTC-4, Stephen Hoffman 
>> wrote:
>>> On 2021-10-06 15:06:49 +0000, pcov... at gmail.com said:
>>>
>>>> has anybody done this successfully and how?
>>>>
>>>> evidently the ciphers on both systems can't agree and close the 
>>>> connection. is it doable if I have a key on both systems that I've 
>>>> generated on my pc? and if so where do I place it on VMS? the 3Par 
>>>> has an add option.
>>>
>>> If you're not on V5.7 ECO5c or higher (ECO5o is current on Itanium, 
>>> and ECO5c is per-call on Alpha), get there, and try ssh again.
>>>
>>> If things fail then, use ssh -vvvvvv and check the results of the 
>>> negotiation for the key exchange and the cipher from what is 
>>> available on both ends of whichever version of 3PAR and OpenVMS 
>>> you're using here.
>>
>> thanks I'll look for it, why didn't anyone from VSI recommend this 
>> when I called it in. sigh
>> I'm on VSI I64VMS TCPIP V5.7-13ECO5B  and I have the latest SSH patch 
>> too.
> 
> Why doesn't OpenVMS itself notify the system administrator^Wmanager that 
> the server is down-revision?  Sigh. Alas, we all get to track this 
> manually, or with our own tooling. VSI does have some new tool arriving 
> here, though details are sparse.
> 
> One VSI ssh patch featured an interesting collection of directions, and 
> the installation instructions were, well, in conflict with the provided 
> files. That boo-boo won't hit your case here, though.
> 
> Fetch ECO5o from the VSI patch server if that's not already installed, 
> and try ssh again.
> 
> Then ssh -vvvvv and check for the details of the negotiation failure, if 
> an error arises.
> 

I moved my hobbyist Alpha onto TCPWare partially for this. Works for me!

Chris


-- 
Chris