Commit graph

7 commits

Author SHA1 Message Date
jlam
1c57323789 Merge packages from the buildlink2 branch back into the main trunk that
have been converted to USE_BUILDLINK2.
2002-08-25 21:48:57 +00:00
zuntum
f09b567537 Strongly-buildlinkify 2001-11-02 09:49:59 +00:00
zuntum
d038a73ebd Move pkg/ files into package's toplevel directory 2001-10-31 22:52:58 +00:00
wiz
433b62957e Move to sha1 checksum, and/or add distfile sizes. 2001-04-21 11:23:08 +00:00
agc
2d6b6a009c + move the distfile digest/checksum value from files/md5 to distinfo
+ move the patch digest/checksum values from files/patch-sum to distinfo
2001-04-17 11:43:32 +00:00
wiz
a13ea108bb Update to new COMMENT style: COMMENT var in Makefile instead of pkg/COMMENT. 2001-02-17 17:52:59 +00:00
hubertf
b38c8eb1be 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 09:12:46 +00:00