From owner-freebsd-security Mon May 24 22:39:22 1999 Delivered-To: freebsd-security@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id 0801514DF1 for ; Mon, 24 May 1999 22:39:20 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id XAA11926; Mon, 24 May 1999 23:39:09 -0600 (MDT) Message-Id: <4.2.0.37.19990524233825.00c03bd0@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.37 (Beta) Date: Mon, 24 May 1999 23:39:04 -0600 To: wkt@cs.adfa.edu.au, freebsd-security@FreeBSD.ORG From: Brett Glass Subject: Re: TCP connect data logger In-Reply-To: <199905250213.MAA02815@henry.cs.adfa.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org That really sucks! But in a good way. ;-) I'd like to see it as a package. --Brett Glass At 12:13 PM 5/25/99 +1000, Warren Toomey wrote: >This is strictly off-topic for FreeBSD, but anyway ... A few people desired >to know why someone was attacking port X on their box. Ages ago, I wrote a >small program, tcpsuck, that is run from inetd. Tcpsuck sits on a port and >logs the data coming in. It stops after a pre-defined timeout, or when the >remote end break the connection. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message