From owner-freebsd-current Tue Mar 12 08:28:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA26804 for current-outgoing; Tue, 12 Mar 1996 08:28:54 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA26797 for ; Tue, 12 Mar 1996 08:28:50 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA12070; Tue, 12 Mar 1996 11:28:40 -0500 Date: Tue, 12 Mar 1996 11:28:40 -0500 From: "Garrett A. Wollman" Message-Id: <9603121628.AA12070@halloran-eldar.lcs.mit.edu> To: Paul Traina Cc: current@FreeBSD.org Subject: Re: finger and 2.2-960303-SNAP In-Reply-To: <199603120135.RAA03399@precipice.shockwave.com> References: <199603112038.NAA03837@phaeton.artisoft.com> <199603120135.RAA03399@precipice.shockwave.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > It interoperates fine with non-broken TCP implementations. I'm really glad > that finger was chosen... of course, it should have been DOCUMENTED. :-) Well, if you think about it, it's pretty clear that `finger' was about the only service which /could/ be changed in this way. Oh, FTP data connections might be T/TCP-ized as well, but it seemed to me that people were rather more likely to get hurt in that instance, so I decided against it. I still haven't gotten around to doing a Sun RPC transport module for T/TCP. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant