[2767] in Kerberos-V5-bugs
telnet/454: telnetd causes terminal windows to hang
daemon@ATHENA.MIT.EDU (root@hpss1.ccs.ornl.gov)
Mon Aug 4 15:34:49 1997
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: hartmans@MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, root@hpss1.ccs.ornl.gov
Date: Mon, 4 Aug 1997 15:32:27 -0400
From: root@hpss1.ccs.ornl.gov
Reply-To: root@hpss1.ccs.ornl.gov
To: krb5-bugs@MIT.EDU
>Number: 454
>Category: telnet
>Synopsis: telnetd causes terminal windows to hang
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: hartmans
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Mon Aug 04 15:33:01 EDT 1997
>Last-Modified:
>Originator: Dan Million
>Organization:
Oak Ridge National Laboratory
>Release: 1.0pl1
>Environment:
IBM RS/6000 model 580, AIX 4.1.4
System: AIX hpss1 1 4 000041156600
>Description:
When we use the Kerberos telnetd, remote users logging into our
machine have their terminal windows hang. Typing a command like
"su root" will do this every time. Sometimes just a control-C
will do it.
I've run telnetd in debug mode, and it appears that the connection
is not really hung; characters are going over the network. But none
of them are visible on the terminal window.
We can't implement our plans to use Kerberized telnet as long as
this situation holds!
Another (possibly related) problem is that frequently telnet sessions
go away and a "login" process is still running on our machine. We
tend to accumulate a dozen or so of these disconnected login processes,
and I have to become root and kill them by hand.
>How-To-Repeat:
More or less described above: install Kerberos version of telnetd;
modify /etc/inetd.conf to replace standard telnetd. Then telnet
to machine where the Kerberos telnetd is installed, using either
Kerberos telnet or plain ol' telnet. Type a control-C or a "su"
command, and watch the terminal window go dead.
>Fix:
None known.
>Audit-Trail:
>Unformatted:
