kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/net/isic/Makefile

21 lines
511 B
Makefile
Raw Normal View History

Merge packages from the buildlink2 branch back into the main trunk that have been converted to USE_BUILDLINK2.
2002-08-25 23:48:57 +02:00
# $NetBSD: Makefile,v 1.4 2002/08/25 21:49:59 jlam Exp $
Import isic-0.05: Ip Stack Integrity Checker (IP, TCP, UDP, ICMP et. al.) ISIC (and components) is intended to test the integrity of an IP Stack and its component stacks (TCP, UDP, ICMP et. al.) It does this by generating a controlled random packet (controlled randomness... wacky huh?). The user can specify he/she/it [I'm tempted to put 'it' before 'she' :-)] wants a stream of TCP packets. He/she/it suspects that the target has weak handling of IP Options (aka Firewall-1). So he/she/it does a 'tcpsic -s rand -d firewall -I100'. And observes the result. A great use for ISIC would be to fire it through a firewall and see if the firewall leaks packets. But of course that would be illegal because Network Associates owns a bogus patent on that :-) You could do that by setting the default route on the sending computer to the firewall..... But that would be illegal. (But I can't legally have a beer so do you think I care about laws?) By far the most common use for these tools is testing IDS systems. A day after I took the source offline and moved it to a cvs server, a half dozen people working on seperate home-grown IDS systems emailed requesting the source be put back up.
2000-11-30 10:12:46 +01:00
#
DISTNAME= isic-0.05
CATEGORIES= net
MASTER_SITES= http://expert.cc.purdue.edu/~frantzen/
EXTRACT_SUFX= .tgz
MAINTAINER= hubertf@netbsd.org
HOMEPAGE= http://expert.cc.purdue.edu/~frantzen/
Update to new COMMENT style: COMMENT var in Makefile instead of pkg/COMMENT.
2001-02-17 18:52:59 +01:00
COMMENT= Ip Stack Integrity Checker (IP, TCP, UDP, ICMP et. al.)
Import isic-0.05: Ip Stack Integrity Checker (IP, TCP, UDP, ICMP et. al.) ISIC (and components) is intended to test the integrity of an IP Stack and its component stacks (TCP, UDP, ICMP et. al.) It does this by generating a controlled random packet (controlled randomness... wacky huh?). The user can specify he/she/it [I'm tempted to put 'it' before 'she' :-)] wants a stream of TCP packets. He/she/it suspects that the target has weak handling of IP Options (aka Firewall-1). So he/she/it does a 'tcpsic -s rand -d firewall -I100'. And observes the result. A great use for ISIC would be to fire it through a firewall and see if the firewall leaks packets. But of course that would be illegal because Network Associates owns a bogus patent on that :-) You could do that by setting the default route on the sending computer to the firewall..... But that would be illegal. (But I can't legally have a beer so do you think I care about laws?) By far the most common use for these tools is testing IDS systems. A day after I took the source offline and moved it to a cvs server, a half dozen people working on seperate home-grown IDS systems emailed requesting the source be put back up.
2000-11-30 10:12:46 +01:00
Merge packages from the buildlink2 branch back into the main trunk that have been converted to USE_BUILDLINK2.
2002-08-25 23:48:57 +02:00
USE_BUILDLINK2= YES
Import isic-0.05: Ip Stack Integrity Checker (IP, TCP, UDP, ICMP et. al.) ISIC (and components) is intended to test the integrity of an IP Stack and its component stacks (TCP, UDP, ICMP et. al.) It does this by generating a controlled random packet (controlled randomness... wacky huh?). The user can specify he/she/it [I'm tempted to put 'it' before 'she' :-)] wants a stream of TCP packets. He/she/it suspects that the target has weak handling of IP Options (aka Firewall-1). So he/she/it does a 'tcpsic -s rand -d firewall -I100'. And observes the result. A great use for ISIC would be to fire it through a firewall and see if the firewall leaks packets. But of course that would be illegal because Network Associates owns a bogus patent on that :-) You could do that by setting the default route on the sending computer to the firewall..... But that would be illegal. (But I can't legally have a beer so do you think I care about laws?) By far the most common use for these tools is testing IDS systems. A day after I took the source offline and moved it to a cvs server, a half dozen people working on seperate home-grown IDS systems emailed requesting the source be put back up.
2000-11-30 10:12:46 +01:00
GNU_CONFIGURE= YES
post-install:
${INSTALL_DATA} ${WRKSRC}/README ${PREFIX}/share/doc/isic.README
Merge packages from the buildlink2 branch back into the main trunk that have been converted to USE_BUILDLINK2.
2002-08-25 23:48:57 +02:00
.include "../../devel/libnet/buildlink2.mk"
Import isic-0.05: Ip Stack Integrity Checker (IP, TCP, UDP, ICMP et. al.) ISIC (and components) is intended to test the integrity of an IP Stack and its component stacks (TCP, UDP, ICMP et. al.) It does this by generating a controlled random packet (controlled randomness... wacky huh?). The user can specify he/she/it [I'm tempted to put 'it' before 'she' :-)] wants a stream of TCP packets. He/she/it suspects that the target has weak handling of IP Options (aka Firewall-1). So he/she/it does a 'tcpsic -s rand -d firewall -I100'. And observes the result. A great use for ISIC would be to fire it through a firewall and see if the firewall leaks packets. But of course that would be illegal because Network Associates owns a bogus patent on that :-) You could do that by setting the default route on the sending computer to the firewall..... But that would be illegal. (But I can't legally have a beer so do you think I care about laws?) By far the most common use for these tools is testing IDS systems. A day after I took the source offline and moved it to a cvs server, a half dozen people working on seperate home-grown IDS systems emailed requesting the source be put back up.
2000-11-30 10:12:46 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink