From owner-freebsd-security Sun Jan 23 4:45:33 2000 Delivered-To: freebsd-security@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id 441C614A04 for ; Sun, 23 Jan 2000 04:45:24 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com (gj-06-112.bta.net.cn [202.106.6.112]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id UAA14709 for ; Sun, 23 Jan 2000 20:42:30 +0800 (CST) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.9.3) id UAA02239 for freebsd-security@freebsd.org; Sun, 23 Jan 2000 20:42:44 +0800 (+0800) (envelope-from robinson) Date: Sun, 23 Jan 2000 20:42:44 +0800 (+0800) From: Michael Robinson Message-Id: <200001231242.UAA02239@netrinsics.com> To: freebsd-security@freebsd.org Subject: tcpdump Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know what the deal is with this comment in tcpdump.c: * (BTW, please don't send us patches to print the packet out in ascii) I've just finished with my latest version of such patches. Does that make me some sort of E133t H4x0r or something? Would applying such patches into the tree cause some sort of global outbreak of evildoing? It certainly isn't any sort of performance issue, because my code, with ascii, is faster than the current code without. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message