On Friday, 05/09/2008 at 09:12 EDT, Tim Joyce <[EMAIL PROTECTED]> wrote:
> I think the problem is, TUBES really is taking control of port 23. One
> of the procedures to setup TUBES telnet, is to take (comment) out the
> PORT 23 statement from PROFILE TCPIP. So, there is no way of letting
> TCPIP know that port 23 is a SECURE port. I think the fact that Macro4
> says secure telnet IS NOT supported, indicates secure telnet will not
> work.
(sigh) There are TWO kinds of secure telnet servers:
1. The SSL tunnel is established BEFORE any telnet traffic begins ("static
SSL")
2. The SSL tunnel is established AFTER telnet protocol negotiation has
started, but before any user data is transferred ("dynamic SSL")
If your TN3270 client supports static SSL, then it should work with TUBES,
as TUBES would be unaware that the SSL session is in effect.
Your PROFILE would show
23 TCP TUBESVM SECURE <label>
Alan Altmark
z/VM Development
IBM Endicott
