[Info-vax] 3par ssh connection

[Stephen Hoffman]

On 2019-05-22 17:10:03 +0000, mepetya said:

> 2019. május 22., szerda 18:42:03 UTC+2 időpontban Stephen Hoffman a 
> következőt írta:
>> So port an ssh client.  Or downgrade the ssh server configuration 
>> requirements.  Or acquire licenses for and upgrade to a current VSI 
>> OpenVMS version.
>> This is not the only problem with the older HPE releases, and the rest 
>> of the world and what most of us are interoperating with will only 
>> continue moving forward.
> 
> Yes, unfortunately, operators say that the security level on the 3par 
> SSH server cannot be changed.

Escalate this whole situation to your management to sort out.  This is 
some of what they get paid to sort.

> I wrote HPE support to resolve access to patches.

That's not going to happen.

> What is the latest patch for HPE TCPIP v5.7?

I've already answered that.

> In the meantime, Process Software has provided a link to the latest 
> patch for SSH v2.4, which is said to meet these security requirements, 
> as required by the 3par SSH server.

That'll probably be the near-term path.

> I can't upgrade to another version of OpenVMS because we no longer have 
> support for the database manager (InterSystems Caché).

In the absence of a change in strategy and plans at Intersystems, your 
management and your requirements have you on a path to port off of 
OpenVMS.

> The easiest thing would be to use another ported SSH client, but 
> unfortunately I don't know one. Do you know someone else I could try?

If there is a port or if there is to be a port, it'd probably start 
here: https://www.openssh.com — but I'm not aware of a port.

The production OpenVMS configurations all have the patches available 
from HPE or VSI, and the hobbyists can downgrade connections and/or can 
use telnet and/or DECnet.



-- 
Pure Personal Opinion | HoffmanLabs LLC