[Info-vax] 3par ssh connection

[Stephen Hoffman]

On 2019-05-22 19:24:50 +0000, Grant Taylor said:

> I'm sure there are MANY nuanced differences.  But what effective 
> difference would a newer version of the TCP/IP stack have on 
> connections?

Better IPv6 support, and IPP, among other details.

http://www.process.com/products/multinet/feature_comp.html

Different management from TCP/IP Services, though.

> I'm ignorant of and naively curious about what has changed in the 
> TCP/IP stack age that you're talking about that could impact what the 
> OP is wanting to do.

Specifically for what the OP is trying to do here with an ssh 
connection to a 3PAR storage controller, and from an unsupported and 
down-revision OpenVMS configuration?  Not much.

The path here is add-on ssh, or HPE support, or an upgrade to and VSI 
support, porting some code, or equivalent.  And that's all fodder for a 
discussion between the OP and local management.

But it's where we're all headed.  VSI IP will be what everybody that's 
staying on support will be using as the vendor IP stack.

The VSI TCPIP package is a fork of Multinet.

VSI does not have the necessary rights to continue with the HPE TCP/IP 
Services product.

> Note:  I'm not considering the ssh client to be part of the TCP/IP 
> stack.  Even if the ssh client is distributed with the stack, IMHO it's 
> still independent of the TCP/IP stack.

ssh, TLS, IP, distributed authentication, and connection security 
are—or should be—components of OpenVMS itself, and not separate.



-- 
Pure Personal Opinion | HoffmanLabs LLC