>>>>> "Burkhardt," == Burkhardt, Andrew <[EMAIL PROTECTED]> writes:
Burkhardt,> Hi, We have setup a test Windows Server 2003
Burkhardt,> Domain/KDC. We have a Windows 2000 Professional
Burkhardt,> computer using the kerberized Ktelnet client,
Burkhardt,> connecting to a Red Hat 9 Linux box running kerberized
Burkhardt,> telnetd, and successfully authenticating using
Burkhardt,> Kerberos. Basically, everything is running correctly
Burkhardt,> in the environment. The problem is we use a
Burkhardt,> non-kerberized telnet client in the field. We are
Burkhardt,> heavily dependant on this client, meaning we can not
Burkhardt,> change clients and fyi, there are no kerberized
Burkhardt,> upgrade for this client. Is there a way to "wrap" a
Burkhardt,> non-kerberized telnet client so it will use kerberos
Burkhardt,> authentication? Has anyone had any experience with
Burkhardt,> this problem? I am looking for any suggestions. Many
Burkhardt,> thanks!
You could use Kerberized ssh to forward the telnet port. You would
not get single sign-on, but you would at least get security.
________________________________________________
Kerberos mailing list [EMAIL PROTECTED]
https://mailman.mit.edu/mailman/listinfo/kerberos
