aboutsummaryrefslogtreecommitdiff
path: root/security/hafiye/pkg-descr
diff options
context:
space:
mode:
authorYing-Chieh Liao <ijliao@FreeBSD.org>2002-08-14 15:53:48 +0000
committerYing-Chieh Liao <ijliao@FreeBSD.org>2002-08-14 15:53:48 +0000
commit5e133f9ad11c6c18913ddc0bb2c085be7198b693 (patch)
tree66b14be72a744cf2c56f835b12dac32d3ef07788 /security/hafiye/pkg-descr
parent455b2dd5013268da671af3adec7b96a5fa92b31d (diff)
downloadports-5e133f9ad11c6c18913ddc0bb2c085be7198b693.tar.gz
ports-5e133f9ad11c6c18913ddc0bb2c085be7198b693.zip
Notes
Diffstat (limited to 'security/hafiye/pkg-descr')
-rw-r--r--security/hafiye/pkg-descr18
1 files changed, 18 insertions, 0 deletions
diff --git a/security/hafiye/pkg-descr b/security/hafiye/pkg-descr
new file mode 100644
index 000000000000..4b80ba1576b1
--- /dev/null
+++ b/security/hafiye/pkg-descr
@@ -0,0 +1,18 @@
+When I looked at the source code for various famous sniffers, I've noticed
+that they all had all seperate .C files for interpreting various protocols.
+Why not have a sniffer that can understand user-supplied protocol details?
+Here it is.
+
+When fired, Hafiye first visits each sub-directory under its knowledge-base
+directory and opens to see whether it is a protocol knowledge-base file. If
+so, It loads the necessary information from that file and places it into its
+memory space. After constructing the supplied knowledge-base, Hafiye starts
+looping for receiving packets. When a packet arrives, it demultiplexes the
+layers according to its knowledge-base and prints protocol-based information.
+
+Features
+ - Multi Platform Support (Posix Compliant)
+ - Customizable Protocol Definitions (Layer II, III and IV)
+ - Customizable Packet Interpretation (Layer II, III and IV)
+
+WWW: http://www.enderunix.org/hafiye/