airpwn - A network security utility
Synopsis
Description
Options
Examples
Notes
Bugs
Author
Website
airpwn -i iface -c configfile -d drivername [-M -C -I -l -f -h -v -k -F]
This manual page documents briefly the airwpn command.airpwn is a thoughtful framework for automated injection of arbitrary application-layer data on an unencrypted 802.11 network. It is used mainly for penetration testing as its primary role is for a complex pattern matching and packet generation.
This program doesnt follow the usual GNU command line syntax. A summary of options is included below.
-i the interface to listen/control/inject with. Equivalent of setting -M -C and -I to the same interface. -M specifies the interface to monitor for packets. This interface must support monitor mode. -C specifies the interface to use for control. (Right now this is only used for changing channels.) -I specifies the interface to use for packet injection. This interface MUST support the ability to inject raw packets. For atheros, this likely is ath0raw. -d the driver name used for the specified interface (e.x. "hostap", "prism54", "madwifiold", "madwifing") -c the location of the configuration file -l the location of the file targeted for verbose logging -f bpf filter for libpcap -k WEP key for packet de/encryption. May be used multiple times to specify multiple keys -F Assume no FCS headers at the end of the 802.11 frames. Some drivers append these and others dont. If WEP decryption is failing when youre positive you have the correct key, try using/not using -F. -h quick help information -v may be called multiple times to increase verbosity
airpwn -i ath0raw -d madwifi -c conf/airpwned_img -vairpwn -i ath0 -I ath0raw -d madwifi -c conf/airpwned_img -F -k 11:22:33:44:55 -v -v -v
This utility was first demonstrated at Defcon 12.
There are no known bugs at this time.
airpwn was written by Bryan Burns <toast@users.sourceforge.net>.
This manual page was written by Jacob Appelbaum <jacob@appelbaum.net>
<http://airpwn.sourceforge.net>
Top of page |
1NSuB | AIRPWN (1) | Jun 30, 2006 |
If you would like to republish one of the articles from this site on your webpage or print journal please contact IronGeek.
Copyright 2020, IronGeek