[1496] in Kerberos-V5-bugs
Re: Kerberos V5 Telnet compliance with RFC1416
daemon@ATHENA.MIT.EDU (Theodore Ts'o)
Tue Jun 20 22:48:32 1995
Date: Tue, 20 Jun 1995 22:48:26 +0500
From: Theodore Ts'o <tytso@MIT.EDU>
To: ramus@nersc.gov
Cc: krb5-bugs@MIT.EDU, johnma@sco.com, jonco@sco.com, dceivers@sco.com
In-Reply-To: Joe Ramus's message of Mon, 19 Jun 95 16:00:26 PDT,
<9506192300.AA21907@windsail.nersc.gov>
Date: Mon, 19 Jun 95 16:00:26 PDT
From: ramus@nersc.gov (Joe Ramus)
I saw the following on the IETF mailer. My question:
Does the Kerberos V5 telnet & telnetd include most of the bug fixes
that are in the version announced by David Borman?
I haven't looked at the latest version to see what bug fixes are there.
A lot of the egregious ones were first found in the V5 version, and most
of the were forwarded back to Berkeley. They may have fixed a few
versions that aren't fixed in ours though.
Before the latest Berkeley telnet release came out, I decided I that I
would stop worring about who had the "change token" on the telnet
release, since we've made so many changes to that telnet can be built
under autoconf that trying to merge changes back and forth probably
wouldn't be worth it. (And the CSRG was supposed to be dead, damn it.
They just keep raising back out of the grave, like a vampire.....)
Our plan is to eventually be able to distribute telnet either in the V5
tree, or as a separate component, using autoconf for its portability,
instead of the manually maintained Makefile system which the Berkeley
telnet currently uses.
- Ted
