Alan Altmark wrote:
> This is incorrect. As of z/VM 5.3 the CMS ftp client, telnet
client, the
ldap client utilities, and the SMTP server (which is also an SMTP client)
are SSL-enabled. This is in addition to the updates to the telnet and ftp
servers to support negotiated (aka "explicit") SSL, as is required to do
secure SMTP, in addition to their existing support for "static" or
"implicit" SSL.
Do the new CMS clients really use the SSL server to do the encryption or
is there encryption code in each client?
The ssh and scp client-side commands have generated more interest than an
ssh server. With an ssh client you do all sorts of automated management
things, including allocating storage in the disk controllers!
Also centralizing userid management, server backups, webserver
configuration.
Thinking about implementing a server, OTOH, gives me a migraine and heart
palpitations. Among other things, it introduces a significant challenge
because of the expectation (reasonable or not) that it would allow
fullscreen interaction. And I'm not convinced the benefit would be worth
the expense.
My first choice would be for the client-side command-line processes. I
understand that creating an inbound SSH protocol server would be
difficult but I would definitely accept a LINEMODE interaction because
I think that the screen manipulation is probably best done on the client
side of that transaction. Let z/VM deliver line by line and let a PuTTY
type program use my PC screen whatever way I set it up.
Alan Altmark
z/VM Development
IBM Endicott
/Tom Kern
