From owner-freebsd-current  Mon Jan 15 13:21:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA09573
          for current-outgoing; Mon, 15 Jan 1996 13:21:40 -0800 (PST)
Received: from interbev.mindspring.com (interbev.mindspring.com [204.180.142.2])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA09567
          for <freebsd-current@freebsd.org>; Mon, 15 Jan 1996 13:21:37 -0800 (PST)
Received: (from rsanders@localhost) by interbev.mindspring.com (8.7.Beta.13/8.7.Beta.2) id QAA29362; Mon, 15 Jan 1996 16:21:33 -0500
Date: Mon, 15 Jan 1996 16:21:33 -0500
From: Robert Sanders <rsanders@mindspring.com>
Message-Id: <199601152121.QAA29362@interbev.mindspring.com>
To: "Garrett A. Wollman" <wollman@lcs.mit.edu>
Cc: -Vince- <vince@apollo.COSC.GOV>, freebsd-current@freebsd.org
Subject: Re: finger problem going from 2.1R to -current 
In-Reply-To: <9601152109.AA11052@halloran-eldar.lcs.mit.edu>
References: <199601152017.PAA28876@interbev.mindspring.com>
	<Pine.BSF.3.91.960115125532.20064d-100000@apollo.COSC.GOV>
Sender: owner-current@freebsd.org
Precedence: bulk

On Mon, 15 Jan 1996 16:09:53 -0500, "Garrett A. Wollman" <wollman@lcs.mit.edu> said:

>> Maybe this can be committed to the tree...

> No.  (There is another, completely different, kernel fix.)

Yeah, the T/TCP changes just recently got put into the tree.  I guess
the importance of T/TCP for this is that it can save, what, one round
trip per finger connection?  What confuses me is that, though I
haven't read rfc1644 or the kernel source, I thought that T/TCP would
properly cope with hosts that didn't want to cooperate.

Otherwise, it seems that the default settings for both rfc* sysctl
options should be off.  TCP extensions just seem to cause trouble for
the Average Joe.

  -- Robert