Jump to content
Hak5 Forums


Dedicated Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


About Zylla

  • Rank
    Developer / Reverse Engineer
  • Birthday 11/22/1988

Contact Methods

  • Skype

Profile Information

  • Gender
  • Location

Recent Profile Visitors

4,281 profile views
  1. I haven't tested the module in a while. I'll see if I can test it today. 🙂 Git can be used on the Pineapples, you just need to install it first. Which can be done using opkg. (Update it first, then install)
  2. @DoJo_Mast3r I did some testing on the pcapng file you mailed me. I also took a look in Wireshark manually. It doesn't seem to contain any PMKID's. (Total of 9 packets. 3 Beacons, 2 Probe Requests, and 4 Probe Responses.)
  3. Have you tried using hcxdumptool on the desktop to get the same PMKID, just to see if you can produce the same result there? Also. Could you share your pcap file?Just email it to me if you don't want it to be public: (adde88@gmail.com)
  4. When hcxdumptool successfully gets a PMKID it will display a message in the terminal. If the Pineapple is within reach of any AP's or clients, it normally takes just a few seconds to get a PMKID. My record was 11 successfuly PMKID's in under a minute. (I did have authorization from the owners) Read the help message, read the github page for hcxdumptool, and try playing with different "enable_status" variables.
  5. @Bigbiz If you're trying to install both hcxtools and hcxdumptool I suggest you read the first post in this thread. You can install the latest version of both tools automatically by issuing the command I have presented in said post. But please remember, you need to SSH into the Pineapple before running the command. PS. The reason you're make command failed is because there is no Makefile, and no need for it. PSS. If you're trying to install/compile the tools for usage on your Kali machine, take a look at ZerBea's github repo. As my repo is solely for the Pineapples.
  6. If you read the output carefully from your first find attempt: "find: unrecognized: ��" at means that there's a symbol in your input that it doesn't recognize. (They don't appear on the screen, so everything looks ok, but is not) Try typing it again. As for me, i just tested the package on my Nano, and it's working perfectly fine. It gets installed to /sbin, or /sd/sbin (if you install to the SD-card) Screenshot of my attempt below :
  7. Strange. After installing, try this: find / -name hcxpcaptool Typing from my cellphone, so sorry for not formating the post correctly.
  8. You seem to have entered the wrong command. It's hcxpcaptool, not hcxcaptool.
  9. Both tools have been updated to follow changes from upstream. We're now at version "16". I've also fixed the "Bus error" message on hcxpcaptool. (Thank @skylark for reporting it) Everything should now work perfectly. ? Please let me know about any issues, and i'll look into them asap. ?
  10. I'll look into it asap.
  11. I just tested the latest release of hcxdumptool on my Nano and my Tetra. No "bus error" when trying it. Screenshot attached.
  12. Hmm.. Anyone else getting the "bus error"? It happened earlier due to some compiler options misconfigured, but I haven't done anything that should cause it to return.
  13. I've updated both tools, and fixed the links in the first post. Also: @Bigbiz asked how to use this on his linux machine. You need to download the original source-code for hcxdumptool and hcxtools, and then compile it. (Make sure you have the necessary dependencies installed)
  14. Links are not updated, but you can check the repo manually to download them until I get them updated tonight ?
  15. Strange. Same command works perfectly for me. I usually start by setting the interface into monitor-mode before running hcxdumptool. But it should also work without doing it (It will set it to monitor mode by itself) I tested the same command on my Tetra, running the latest version of hcxdumptool, and no issues. Are you having issues with your Tetra when doing other things as well? I've seen some people having identical issues when doing other stuff, like running PineAP, etc.