tools
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tools [2007/02/04 22:00] – darkaudax | tools [2018/06/18 03:48] (current) – Added kstats mister_x | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Tools ====== | ====== Tools ====== | ||
- | |||
- | |||
===== WZCook ===== | ===== WZCook ===== | ||
It recovers WEP keys from XP's Wireless Zero Configuration utility. This is experimental software, so it may or may not work depending on your Service Pack level. | It recovers WEP keys from XP's Wireless Zero Configuration utility. This is experimental software, so it may or may not work depending on your Service Pack level. | ||
Line 9: | Line 7: | ||
network={ | network={ | ||
| | ||
- | | + | |
+ | } | ||
- | If you don't use WZC service, but you use USR Utility, get this registry value and try it [[http:// | + | The WZCook tool also supports a silent mode. This is invoked by adding " |
+ | |||
+ | If you don't use WZC service, but you use USR Utility, get this registry value and try it [[http:// | ||
HKey_Current_User/ | HKey_Current_User/ | ||
===== ivstools ===== | ===== ivstools ===== | ||
- | You can handle //.ivs// files with this tool. You can either merge or convert them. | + | This tool handle //.ivs// files. You can either merge or convert them. |
==== Merge ==== | ==== Merge ==== | ||
- | Use --merge option to merge multiple //.ivs// files. Example: | + | Use -'''' |
ivstools --merge dump1.ivs dump2.ivs dump3.ivs out.ivs | ivstools --merge dump1.ivs dump2.ivs dump3.ivs out.ivs | ||
It will merge dump1.ivs, dump2.ivs and dump3.ivs into out.ivs. You can merge more than 2 files, output file must be the last argument. | It will merge dump1.ivs, dump2.ivs and dump3.ivs into out.ivs. You can merge more than 2 files, output file must be the last argument. | ||
Line 29: | Line 30: | ||
==== Convert ==== | ==== Convert ==== | ||
- | Use --convert option to convert a pcap file (by default, they have //.cap// extension) to a //.ivs// file. Example: | + | Use -'''' |
ivstools --convert out.cap out.ivs | ivstools --convert out.cap out.ivs | ||
It will save out.cap IVs to out.ivs | It will save out.cap IVs to out.ivs | ||
Line 37: | Line 38: | ||
**Note**: Kismet produce pcap files (the extension is //.dump//), that can be converted | **Note**: Kismet produce pcap files (the extension is //.dump//), that can be converted | ||
- | **WARNING**: | + | **WARNING**: |
+ | |||
+ | ===== Versuck-ng ===== | ||
+ | |||
+ | versuck-ng' | ||
+ | |||
+ | Usage: versuck-ng options -m -e | ||
+ | |||
+ | Options: | ||
+ | -h, --help | ||
+ | -m MAC, --mac=MAC | ||
+ | -e ESSID, --essid=ESSID essid | ||
+ | |||
+ | Use: | ||
+ | versuck-ng -e ESSID -m WIRED_MAC | ||
+ | |||
+ | ===== buddy-ng ===== | ||
+ | |||
+ | Check out [[easside-ng]] documentation. | ||
+ | |||
+ | ===== makeivs-ng ===== | ||
+ | |||
+ | makeivs-ng is a tool designed to generate an IVS dump file with an inputted WEP key. The aim of is tools is to provide a way to create dumps with a known encryption key for tests. | ||
+ | |||
+ | By default, it will generate a file with the BSSID 01: | ||
+ | |||
+ | ^Option^Description^ | ||
+ | |-b < | ||
+ | |-f <num> or --first < | ||
+ | |-k <key> or --key < | ||
+ | |-s <num> or --seed < | ||
+ | |-w < | ||
+ | |-c <num> or --count < | ||
+ | |-d <num> or --dupe < | ||
+ | |-e <num> or --error < | ||
+ | |-l <num> or --length < | ||
+ | |-n or --nofms|Ignores weak IVs.| | ||
+ | |-p or --prng|Use random values when generating IVs. Default is to use sequential values.| | ||
+ | |||
+ | Minimum required parameters: -w and -k. | ||
+ | |||
+ | ===== kstats ===== | ||
+ | |||
+ | kstats is a tool designed to show the FMS algorithm votes for an IVS dump with a specified WEP key. The IVS dump can be get by using the combination of both [[airodump-ng]] and [[# | ||
+ | |||
+ | Usage: | ||
+ | |||
+ | |
tools.1170622806.txt.gz · Last modified: 2007/02/04 22:00 (external edit)