[Info-vax] 3par ssh connection

[Kerry Main]

> -----Original Message-----
> From: Info-vax <info-vax-bounces at rbnsn.com> On Behalf Of Simon Clubley
> via Info-vax
> Sent: May 23, 2019 8:33 AM
> To: info-vax at rbnsn.com
> Cc: Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP>
> Subject: Re: [Info-vax] 3par ssh connection
> 
> On 2019-05-22, Grant Taylor <gtaylor at tnetconsulting.net> wrote:
> >
> > 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.
> >
> > 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.
> >
> 
> It's still layered on top of the TCP/IP stack and in the VMS world, they
tend to
> be shipped as part of the same product.
> 
> The problem is that the HPE SSH client as shipped in the version the OP is
> using is _way_ behind in terms of supported encryption standards and so
> cannot talk to modern more secure security setups.
> 
> TCP/IP support in VMS (both the base stack and higher level applications)
is
> not exactly a strong point of the operating system unfortunately.
> 

Which is why VSI is replacing the current stack with a totally new and much
more modern TCPIP stack based on Multinet. 

Based on VSI stated directions, the old stack will only be optional for a
period of time and then the new stack will be the only one offered.


Regards,

Kerry Main
Kerry dot main at starkgaming dot com