On May 9, 2008, at 8:16 AM, Huegel, Thomas 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.
Well...maybe, maybe not.,
Take a look at how the secure option is done with SSLSERV.
I don't actually know that this will work with arbitrary programs (and
a thorough reading of the manual may prove that it won't), but....if
you AUTOLOG SSLSERV and add SECURE CERTNAME to the end of the inetd-
equivalent entry in PROFILE TCPIP (something like:
992 TCP TUBES SECURE MYCERT NOAUTOLOG
)
Then you *might* end up with a secure TUBES.
It'd be worth a 5-minute try, anyway.
Or, now that I've brought it up, we can just wait 15 minutes, and
Alan, who never sleeps, will say, "No, that doesn't work, sorry."
Adam
