zerbea/hcxdumptoolSmall tool to capture packets from wlan devices.
A tool to capture packets from WLAN devices and to discover potential weak points within own WiFi networks by running layer 2 attacks against the WPA protocol.
Designed to run (mostly headless) on small systems like a Raspberry Pi Zero.
A tool to handle NMEA 0183 sentences from GPS devices.
Designed to run (mostly headless) on small systems like a Raspberry Pi Zero.
A set of tools by ZerBea intended for processing capture files.
A write-up by Ido Hoorvitch from CyberArk covering the statistics of WPA/WPA2 password cracking.
A section of this README that covers hcxdumptool's abilities and the responsibilities of using it.
hcxdumptool uses the modern pcapng format, allowing for use with wireshark or tshark.
It does not crack WPA PSK related hashes. (Use Hashcat or JtR to recover the PSK.)
It does not crack WEP. (Use the aircrack-ng suite instead.)
It does not crack WPS. (Use Reaver or Bully instead.)
It does not decrypt encrypted traffic. (Use tshark or Wireshark in parallel.)
It does not record all traffic captured on the WLAN device. (Use tshark or Wireshark in parallel.)
It does not perform Evil Twin attacks.
It does not provide a beautiful status display.
It is not a honey pot.
Unsupported: Windows OS, macOS, Android, emulators or wrappers!
[!NOTE]
hcxdumptool does not perform conversion or cracking! It is designed to be used in conjunction with the following tools:
Tool Description hcxnmealog Tool to handle NMEA 0183 sentences hcxpcapngtool Tool to convert raw PCAPNG files to Hashcat and JtR readable formats. (hcxtools) hcxhashtool Tool to filter hashes from HC22000 files based on user input. (hcxtools) hcxpsktool Tool to get weak PSK candidates from HC22000 files. (hcxtools) hcxeiutool Tool to calculate wordlists based off ESSIDs gathered. (hcxtools) Hashcat/JtR Third party tools used to infer PSK from HC22000 hash files.
hcxdumptool -> hcxpcapngtool -> hcxhashtool (additional hcxpsktool/hcxeiutool) -> Hashcat or JtR
You might expect me to recommend that everyone should be using hcxdumptool/hcxtools. But the fact of the matter is, however, that hcxdumptool/hcxtools is NOT recommended to be used by inexperienced users or newbies. If you are not familiar with Linux generally or if you do not have at least a basic level of knowledge as mentioned in section "Requirements", hcxdumptool/hcxtools is probably not what you are looking for. However, if you have that knowledge this tools can do magic.
[!IMPORTANT]
While hcxdumptool and hcxtools are available through the package manager on most distributions, these packages are usually very old and outdated, thus cloning and building is recommended.
Make sure that your distribution is updated to its latest version and make sure that all header files and dependencies have been installed BEFORE attempting to compile!
The packages mentioned in the "Requirements" section sometimes come under different names in a package manager! Make sure to install the correct packages!
git clone https://github.com/ZerBea/hcxdumptool.git
cd hcxdumptool
Compiling:
make -j $(nproc)
Installing to /usr/bin:
make install (as super user)
Or installing to /usr/local/bin:
make install PREFIX=/usr/local (as super user)
[!TIP]
On headless operation, remove -DSTATUSOUT from the Makefile before compiling! That way, the status display will not be compiled. This will save CPU cycles and prevent ERRORs from occurring.
It is theoretically possible to compile hcxdumptool for other systems (e.g. Android) and other distributions (e.g. KALI) and other operating systems (BSD) as well. There is no plan to support the operating systems and feature requests will be rejected.
[!WARNING]
Do not expect flawless drivers on brand new hardware!
Driver must support monitor mode and full packet injection!
PRISM devices are not supported!
WIRELESS EXTENSIONS are deprecated and no longer supported!
[!NOTE]
Manufacturers do change chipsets without changing model numbers. Sometimes they add (v)ersion or (rev)vision. As long as a manufacturer or a company does not consider it necessary to supply drivers to the Linux kernel avoid to buy this products!
Always verify the actual chipset with 'lsusb' and/or 'lspci'!
No support for a third party driver which is not part of the official Linux kernel, because there are hundreds of them in the wilderness. I don't have the time for it, nor do I want to. Report related issues to the site, from which you downloaded the driver.
No support for a driver which doesn't support monitor mode and full frame injection natively. If you need these features, do a request on Bugzilla.
Several device and driver tests can be found here. Dependent on the version of the Linux kernel (especially the older ones), expect massive driver issues.