[5601] in Kerberos

home help back first fref pref prev next nref lref last post

krb5-b4 telnet on solaris 2.4

daemon@ATHENA.MIT.EDU (David Parter)
Thu Aug 3 19:19:42 1995

To: kerberos@MIT.EDU
Date: Thu, 03 Aug 1995 17:50:06 -0500
From: David Parter <dparter@cs.wisc.edu>

This isn't really a kerberos problem per se, but is related and I am 
hoping that someone here has seen this and maybe has a fix...

I installed the telnet client from krb5 beta 4 on all our
workstations. I had to do a little bit with autoconf to get it to work
on solaris, but  that was mostly for telnetd, not telnet.

It works great everywhere, except on solaris. The telnet client will
stop, with no more input, when a lot of data is being transfered from
the other end. One reliable way to make this happen is to "ls" a large
directory, or cat a large file.

At one point in my debugging, I thought the client was getting spurious
"urgent" data indication from select(), with no data to read.
I put in a work around for that, and I thought it was fixed (it *looked*
like it was fixed). Now, however, as far as I know, nothing else has
changed, but  with or without my work-around, it has the problem. Also,
I am no longer detecting the spurious urgent data, instead, there is
never anything to read from the net.

I should mention that it doesn't matter what the other end is -- sun,
hp, decstation... although they are probably all running the beta4
telnetd too (for sure it makes no difference with or without encryption).

any ideas? this is driving me nuts...

thanks,

	--david

ps: I know that this problem report does not have enough information --
the problem is, right now I don't know what is going on.

home help back first fref pref prev next nref lref last post