openbsd-ports/net/tcpflow/Makefile

# $OpenBSD: Makefile,v 1.14 2004/12/16 00:31:26 alek Exp $

COMMENT=	"tool for capturing data from TCP connections"

DISTNAME=	tcpflow-0.21
CATEGORIES=	net
MASTER_SITES=	ftp://ftp.circlemud.org/pub/jelson/tcpflow/

HOMEPAGE=       http://www.circlemud.org/~jelson/software/tcpflow/

# GPL
PERMIT_PACKAGE_CDROM=	Yes
PERMIT_PACKAGE_FTP=	Yes
PERMIT_DISTFILES_CDROM=	Yes
PERMIT_DISTFILES_FTP=	Yes
WANTLIB=		c pcap 

CONFIGURE_STYLE=        gnu

.include <bsd.port.mk>
Add WANTLIB markers 2004-12-15 19:31:20 -05:00			`# $OpenBSD: Makefile,v 1.14 2004/12/16 00:31:26 alek Exp $`
net: integrate COMMENT, bump NEED_VERSION. 2001-05-06 00:59:54 -04:00
			`COMMENT= "tool for capturing data from TCP connections"`
add tcpflow port; jethro@dqc.org - tcpflow is a program that captures data transmitted as part of TCP connections (flows), and stores it in a way that is convenient for protocol analysis or debugging. A program like 'tcpdump' only shows a summary of packets seen on the wire, but usually doesn't store the data that's actually being transmitted. In contrast, tcpflow reconstructs the actual data streams and stores each flow in a separate file for later analysis. tcpflow understands sequence numbers and will correctly reconstruct data streams regardless of retransmissions or out-of-order delivery. However, it currently does not understand IP fragments; flows containing IP fragments will not be recorded properly. Note: this port includes a small patch that adds the capability of reading the packets from a tcpdump(1) capture file, using a new option (-r). 1999-11-12 09:22:25 -05:00
Update to 0.21, fixes a format string vulnerability: http://www.atstake.com/research/advisories/2003/a080703-2.txt Not exploitable as it is not installed setuid root. from MAINTAINER. 2003-08-11 20:59:46 -04:00			`DISTNAME= tcpflow-0.21`
add tcpflow port; jethro@dqc.org - tcpflow is a program that captures data transmitted as part of TCP connections (flows), and stores it in a way that is convenient for protocol analysis or debugging. A program like 'tcpdump' only shows a summary of packets seen on the wire, but usually doesn't store the data that's actually being transmitted. In contrast, tcpflow reconstructs the actual data streams and stores each flow in a separate file for later analysis. tcpflow understands sequence numbers and will correctly reconstruct data streams regardless of retransmissions or out-of-order delivery. However, it currently does not understand IP fragments; flows containing IP fragments will not be recorded properly. Note: this port includes a small patch that adds the capability of reading the packets from a tcpdump(1) capture file, using a new option (-r). 1999-11-12 09:22:25 -05:00			`CATEGORIES= net`
			`MASTER_SITES= ftp://ftp.circlemud.org/pub/jelson/tcpflow/`

- Bump NEED_VERSION - Add HOMEPAGE - Remove FAKE=Yes - GNU_CONFIGURE -> CONFIGURE_STYLE - Add @comment to PLIST 2000-10-05 21:41:08 -04:00			`HOMEPAGE= http://www.circlemud.org/~jelson/software/tcpflow/`

I was going to add "# GPL" comment as part of the tcpflow update but jolan@ beat me to the punch. 2003-08-11 21:24:24 -04:00			`# GPL`
license 2000-03-22 19:47:39 -05:00			`PERMIT_PACKAGE_CDROM= Yes`
			`PERMIT_PACKAGE_FTP= Yes`
			`PERMIT_DISTFILES_CDROM= Yes`
			`PERMIT_DISTFILES_FTP= Yes`
Add WANTLIB markers 2004-12-15 19:31:20 -05:00			`WANTLIB= c pcap`
license 2000-03-22 19:47:39 -05:00
- Bump NEED_VERSION - Add HOMEPAGE - Remove FAKE=Yes - GNU_CONFIGURE -> CONFIGURE_STYLE - Add @comment to PLIST 2000-10-05 21:41:08 -04:00			`CONFIGURE_STYLE= gnu`
add tcpflow port; jethro@dqc.org - tcpflow is a program that captures data transmitted as part of TCP connections (flows), and stores it in a way that is convenient for protocol analysis or debugging. A program like 'tcpdump' only shows a summary of packets seen on the wire, but usually doesn't store the data that's actually being transmitted. In contrast, tcpflow reconstructs the actual data streams and stores each flow in a separate file for later analysis. tcpflow understands sequence numbers and will correctly reconstruct data streams regardless of retransmissions or out-of-order delivery. However, it currently does not understand IP fragments; flows containing IP fragments will not be recorded properly. Note: this port includes a small patch that adds the capability of reading the packets from a tcpdump(1) capture file, using a new option (-r). 1999-11-12 09:22:25 -05:00
			`.include <bsd.port.mk>`