Date: Sat, 13 May 95 20:23:51 MDT From: terry@cs.weber.edu (Terry Lambert) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Cc: henrich@crh.cl.msu.edu, freebsd-bugs@FreeBSD.org Subject: Re: bin/396: telnetd problems fix. Message-ID: <9505140223.AA04228@cs.weber.edu> In-Reply-To: <199505140147.SAA01094@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 13, 95 06:47:09 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> I disagree, and we have been down this road at least 4 times in the > last 2 years with FreeBSD. The bug is not in the FreeBSD code, it should > not be bandaided to work with code that gets option negotiation wrong. > > I don't like to fix bugs in other software by making FreeBSD slower at > *anything*. Go get NCSA and FTP software to fix there very ancient > and broken code, they have had 2 years to do this, and still have not. Change the offer/accept order in BSD so it does not appear to be a 4.2 system to this software (without impacting the actual algorithm for doing the negotiation) and the problem will disappear. The option ordering is commutative as far as BSD is concerned, but associative as far as the malfunctioning clients are concerned. It costs nothing and fixes many things to commute the BSD order to change the clients opinion of the association. Other than that, you're right: we've been down the road before and it doesn't need a big rehash. All the opinions "A is broken; fix A", "B is broken, fix B", and "A is broken, fix B" have been restated. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9505140223.AA04228>