
                      ___      ______      _       _
                    /     \   |   _   \   |  \   /  |
                   |  / \  |  |  |  \  |  |   \_/   |
                   | |___| |  |  |_ /  |  |   \_/   |
..oO  THE          |  ---  |  |       /   |  |   |  |         CreW Oo..
                   '''   '''   '''''''    ''''   ''''
                               presents


		      [ ADMfzap 0.1 by plaguez ]

	  a libdl-based connect() and bind() wrapper that
	  helps bypassing poorly configured packet filters.


ADMfzap makes all (or most of) your connect() and bind()
calls originating from port 20 (tcp, ftp-data) or 53 (udp,
dns). Alternatly, the source port can also be configured
via the environment variable $LOPORT.

It redirects the connect() and bind() socket calls to 
custom routines using libdl capabilities.

	
ADMfzap was designed to be fairly portable on
systems using libdl dynamic linker capabilities, and
of course dynamically-linked network executables
(ie: telnet, rpcinfo, ...).

Note that some systems, like FreeBSD, use static executables,
rendering ADMfzap useless.


	Usage:
	------

- untar the archive
- make it (supply the name of your system as only make cmdline argument)
- try it with ./TEST
  It assumes that there is an ftpd listening on port 21 of the local machine.
  Check if it worked by switching to another vt and issuing a netstat cmd.
  It should show you the connexion to localhost:21 originating from localhost:ftp-data.

  If not, well output error messages are usually pretty explicit, the most
  common error being of course ports 20/53 already in use.
 
- real world use during penetration tests would be something like:

  export LD_PRELOAD=./fzap.so
  rpcinfo -p target.box.ADM.NET
  telnet target.box.ADM.NET
  ...


	Credits:
	--------

	K2: porting to Solaris+few mods
	stranNer: porting to FreeBSD.


	The end:
	--------

