From owner-freebsd-security Mon Sep 13 12:13:22 1999 Delivered-To: freebsd-security@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 1EE73155AD for ; Mon, 13 Sep 1999 12:13:12 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA31264; Mon, 13 Sep 1999 15:12:58 -0400 (EDT) (envelope-from wollman) Date: Mon, 13 Sep 1999 15:12:58 -0400 (EDT) From: Garrett Wollman Message-Id: <199909131912.PAA31264@khavrinen.lcs.mit.edu> To: "Rodney W. Grimes" Cc: freebsd-security@FreeBSD.ORG Subject: Re: How to prevent motd including os info In-Reply-To: <199909130222.TAA31984@gndrsh.dnsmgr.net> References: <199909130110.VAA27314@khavrinen.lcs.mit.edu> <199909130222.TAA31984@gndrsh.dnsmgr.net> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Cc's massively snipped.] < said: > Okay, are SYN * ^URG * ^PSH * FIN packets, another words packets with > just the SYN and FIN bits set, but not the others used anyplace other > than in T/TCP aka rfc1644? The finger client used to do this, before it was pointed out to me that the finger specification does not allow it. fetch also tries to do it (or at least tried; I haven't paid attention to the changes in fetch recently). I don't think the TCP in -current will generate such segments, although it will process them correctly. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message