From owner-p4-projects@FreeBSD.ORG Wed Aug 20 15:09:55 2008 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id C999E1065686; Wed, 20 Aug 2008 15:09:55 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E9CA106567E for ; Wed, 20 Aug 2008 15:09:55 +0000 (UTC) (envelope-from rpaulo@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 784818FC15 for ; Wed, 20 Aug 2008 15:09:55 +0000 (UTC) (envelope-from rpaulo@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.2/8.14.2) with ESMTP id m7KF9ogS096909 for ; Wed, 20 Aug 2008 15:09:50 GMT (envelope-from rpaulo@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.2/8.14.1/Submit) id m7KF9oZ2096907 for perforce@freebsd.org; Wed, 20 Aug 2008 15:09:50 GMT (envelope-from rpaulo@FreeBSD.org) Date: Wed, 20 Aug 2008 15:09:50 GMT Message-Id: <200808201509.m7KF9oZ2096907@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to rpaulo@FreeBSD.org using -f From: Rui Paulo To: Perforce Change Reviews Cc: Subject: PERFORCE change 147929 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2008 15:09:56 -0000 http://perforce.freebsd.org/chv.cgi?CH=147929 Change 147929 by rpaulo@rpaulo_epsilon on 2008/08/20 15:09:48 Fill this file with information. Affected files ... .. //depot/projects/soc2008/rpaulo-tcpad/README#2 edit Differences ... ==== //depot/projects/soc2008/rpaulo-tcpad/README#2 (text+ko) ==== @@ -1,1 +1,14 @@ -TCP anomaly detector project +TCP Anomaly Detector +-------------------- + +TCP anomaly detector, tcpad for short, monitors your TCP connections via +libpcap(3) and tries verify the correctness of the TCP stacks. + +We do this by emulating virtual TCP stacks for each end. Whenever an error +occurs, we dump the packets into a pcap(3) file and the state of each virtual +TCP stack. +With this information, you can see if there is indeed a problem with the +operating system you are analyzing or if it's just a false positive from +tcpad. + +-- Rui Paulo