pdump - dumps, greps, monitors, creates, and modifies traffic on a network


This file is here to tell why what I'm hoping to have done soon in the
future, and also to tell why certain things are happening to pdump.
Updates needed and will be added shortly...

Questions, etc. can be sent to either #pdump on SUIDNET (irc.LucidX.com) or
through email at commport5@lucidx.com

Things I want done for the future:
   - Mailing list to be set up...
   - Password sniffing to be added:
     SMTP, poppass, NNTP, SNMP, LDAP, OSPF,
     Rlogin, RIP, NFS, YP/NIS, SOCKS, X11, CVS, SMB,
     PostgreSQL, Meeting Maker, Citrix ICA, Symantec
     pcAnywhere, NAI Sniffer, Oracle SQL*Net, Samba,
     Sybase, and Microsoft SQL auth info
   - I want all libraries to be put into modules
     This has already been started and you can see
     how far it's gone by looking at the pdump/
     directory on http://dev.lucidx.com/
     If you're interested in development, join
     #pdump on SUIDnet (irc.LucidX.com) or justdrop
     me an email (commport5@lucidx.com) and we can
     discuss.  There are already a few people
     which are helping with the development of 
     pdump and hopefully it will become a good
     development team.
   - Other stuff was here but most of it is either
     done or being worked on.

Why [modules and stuff]?
-  Why I wanted to not use modules...
   I didn't want to have to worry about the user
   upgrading a module and one of the subroutines
   in that module will stop working, and that sub
   may be used in pdump.  Also, I don't want the
   user to have to install an entire bundle of
   modules when pdump only uses one or two
   subroutines from it.  And last, I want to be
   able to easily take the libraries and put them
   into pdump:: modules in the future.

-Sam Kamkar [CommPort5@LucidX.com]