Zylla

Active Members
  • Content count

    248
  • Joined

  • Last visited

  • Days Won

    13

5 Followers

About Zylla

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

Profile Information

  • Gender
    Male
  • Location
    Norway

Contact Methods

  • Skype
    adde88@gmail.com

Recent Profile Visitors

2,004 profile views
  1. If i understood the OP correctly; you believe the kernel-change might have been the cause of your problems with Reaver. If it was me i would simply try to compile different kernel-versions myself, to see if it fixes the issue. Usually you can find the .config file for your current kernel within the /boot directory. (At least on Kali/ Debian) You can then copy this .config file to whatever custom kernel you are trying to build, to make it compile with the same settings, or to perhaps look at the differences.
  2. Hi @m0nk666! Everything looks to be in order. You will know if the /sd directory is mounted correctly if you can read/write to it, and it gets saved to the USB-drive. You can also check your dmesg and logread for strings that seems error-related if you're worried. If you get any problems make sure you provide me the at least the output from those two, it makes debugging alot easier. Happy pen-testing! :)
  3. Small Update: Sensepost has decided to use the "SSID-filter patch" on their upstream branch. This was added to my dev-branch some months ago. I decided to also add this to my upstream, as i want it to follow the work of Sensepost as much as possible. Version bumped to: 2.6-4 By default Mana will respond to all probe-requests. This patch allows you to use a whitelist-file, containing the SSID's you want to allow Mana to respond to. All other probe-requests will be ignored If you encounter any issues with this version, or with the newest feature, please inform me :)
  4. To the guy that needed help editing the launch-script, to launch hostapd-mana in "verbose mode": Start by opening the launch-script in your favourite editor. It should be located: /usr/sbin/launch-mana Now go to line number 330. And you will find a bash-function named: hostapd-mana_start It normally looks like this: function hostapd-mana_start { hostapd-mana "$conf" | tee "$mana_output_file" & } Now, edit it. So it looks like this: function hostapd-mana_start { hostapd-mana -d "$conf" | tee "$mana_output_file" & } The only thing i have changed is that i've added: -d To make it even more verbose you can use: -dd, or: the most verbose setting: -ddd
  5. When you're installing this Toolkit on the NANO, you can safely ignore all the lines that are looking like this: grep: /usr/lib/opkg/info/tinyproxy.control: No such file or directory cat: can't open '/usr/lib/opkg/info/tinyproxy.list': No such file or directory I'm guessing that the overlay file-system being used on the Nano, seems to fool the package-manager into believing it's missing some files. When it's really not missing them at all. About the error-messages in your dmesg: It seems that you are using a SD-card. I don't know if that was intended or not, i'm just pointing it out, just in case Those error messages are exactly identical to the ones i am getting when using i'm using my SD-cards. To answer yoru last question: Here are the GitHub repos for the OpenWRT-SDK used by Hak5 to build firmware/software/kernel for your Pineapple: https://github.com/WiFiPineapple/openwrt-pineapple-tetra https://github.com/WiFiPineapple/openwrt-pineapple-nano It's really just a normal OpenWRT-SDK with a few hardware-specific changes. The problem with these repos. are that they are not up-to-date. They uploaded this to GitHub in December, but the repo. is older than that, and uses kernel version 3.18.20. So i took the repo. and simply merged it with upstream OpenWRT, which basically gets it up to date. (You will need to handle conflicts manually though, but there's usually not that many.) The SDK will basically build a normal OpenWRT firmware-file, for the Pineapples. They will NOT contain the web-interface for the Pineapples, or any of the custom Hak5 stuff like PineAP, Pinesniffer, etc. As these programs are closed-source. But can be used to build custom kernels, or other stuff. If you're interested in testing the Mana Toolkit Module for the Pineapple, it can be found at my GitHub repo. while still being developed: https://github.com/adde88/ManaToolkit
  6. Yes. When the bug occurs/triggers, the SD-card interface will "reset". You can see this happening in dmesg / logread. It will usually take a second or two to reset, and when it's done resetting it has a new device-identifier each time. (sda,sdb,sdc,sdd,sde,sdf,sdg, and so on...) After it's done resetting you will be able to read/write again, until it happens again. It's this time-frame when the SD-card is "offline" that makes it easy to detect when using this Toolkit, because it's using alot of processes. When you're doing all the other normal stuff you can do with the Nano, you will usually not detect this bug happening, because it takes only a second or two until it's back up. As i said above: My first encounter with this issue, was when i purchased the Nano and started using custom stuff, and terminal stuff like wifite. It would always crash after a little while, with python complaining about not being able to read/write to the SD-card log-directory. So a quick dive into dmesg revealed that a kernel-module that handles the file-system and journal was crashing when doing stuff on the SD-card. Even simply scanning the SD-card with this command will trigger the bug every time for me, on several different SD-cards i've tested: badblocks -e 100 -v /dev/sdcard/sd1 I very much want to release the Mana Toolkit Module to the official Hak5-repositories, and keep on improving it! But this sd-card issue is worrying me. It gets silly if every Nano-owner needs to insert a thumb-drive to get a Module working. IF anyone owns a Pineapple Nano and is using a SD-card successfully with the Mana Toolkit, PLEASE REPORT BACK TO ME! If i don't get any such reports, i need to assume that everyone will get this issue on the Nano. I don't want that to happen! I really want to keep on improving this for both the Nano and the Tetra. Utilizing the small size of the Nano to run this attack very stealthy from your pocket, or utilizing the size of the Tetra to run a powerful EAP attack on the 2.4 and 5GHz bands at the same time, this would be awesome. And just to update you guys: I'm getting some spare-time in a few days. I will be investing those days heavily in improving this Module and Toolkit. So keep your eyes (and repositories) up for updates! ;)
  7. I'm not 100% sure if the SD-card issue will happen with everyone. (Though i have my suspicions) If i'm correct with it really being a bug within a kernel-module, then many people (maybe even everyone) will have this bug. The problem is that it's really subtle/stealthy, which only makes the bug really evident when doing "lots of work". (Even wifite will trip my sd-card!) To find out what's really happening you can launch two terminals. One where you are installing, and on the other one run this command: tail -f | dmesg This will show you the output from dmesg, live as it's happening. So you don't have to launch dmesg after the bug has happened.
  8. The cause of your problems are related to memory. The process reports an oom error, as well as the other issues you are describing. There is however a quick fix! I noticed this in your dmesg output: 0 pages in swap cache Swap cache stats: add 0, delete 0, find 0/0 Free swap = 0kB Total swap = 0kB If you are running Mana Toolkit on the Nano without any swap, you WILL run into issues! The processes that are launched are so memory and CPU intensive, that even with swap you will get latency issues. (Especially on the Nano!) This problem is really apparent if several clients are connected. Especially when said clients are surfing the web. (More stuff to decrypt on the fly!) This is why i put a limit into the hostapd-config regarding how many clients that it will accept simultaneously. To fix your issue you need to create a swap partition on your usb-drive.
  9. Interesting. I've never experienced this. If it happens again, please try to get the output from dmesg and logread aswell. hostapd-mana does also have a "verbose/debug" setting, which is enabled by: -d (Add more D's to make it more verbose -> -d, -dd, -ddd) You would need to edit the launcher-script to make it launch in verbose-mode, but if you are having troubles editing it just shout out and i can help you.
  10. I am aware of an issue regarding dnsmasq (the software that provides the client with an ip-address) on this toolkit. It's not supposed to shutdown the already running process of dnsmasq (the one running on wlan0 - Managment AP) It is also supposed to restart this service when stopping Mana, if it's not running. But it's not doing this correctly, and i haven't had time enough to push a fix yet. But i'll try to get it fixed soon. I know it's really annoying.
  11. Yeah it looks like it. The device id of your sd-card reader is almost identical to the emdedded sd-card reader on my Nano. Your ID: 05e3:0723 My ID: 05e3:0745 So it's most likely using the exact same drivers as it normally would. You could try to format the sd-card again, for example by tweaking the same script that the web-interface uses when you format the embedded one. It should be located here: /pineapple/modules/Advanced/formatSD/format_sd Just replace all the references from /dev/sdcard/sd1 and /dev/sdcard/sd2 to: /dev/sdb1 and /dev/sdb2 sd2 = swap partition sd1 = ext4 partition This could be worth trying.
  12. That sd-adapter on the usb-port could actually work, depending on where this bug is exactly, and depending on the chipset of your sd-card reader. If that adapter uses the same "kernel-drivers" as the embedded one i can guarantee that it willl be the same. If it uses another driver it gets more interesting. But i'm de-railing a bit. (It could be worth testing to debug this sd-card issue) If it where me i'd just use a normal memory-stick. Installation on that takes a couple of minutes, which it also should on a normal sd-card installation without any bugs. To check if you are getting any of these bugs while installing on a sd-card, just type dmesg in the terminal after the install. If any bugs are happening it should show-up in the output.
  13. Git works perfectly on the Nano and Tetra. opkg install git git-http --dest sd
  14. Installation on a SD-card seems to "not always be working." I'm actually not 100% sure if everyone will experience the kernel-bug, but i'm fairly certain that they will. I therefore removed my sd-card totally, and used a memory-stick mounted as /sd/ It seems like you're doing everything correctly. Like @kbeflo i was going to suggest that you try creatig the /sd dir. But it looks like that didn't work. Which is a bit strange. Also, you should create a swap-partition. Perhaps try a factory-reset? :)
  15. Sorry, i didn't pick up on that you've already tested it on another AP. Well... That's confusing to say the least. Especially considering that mdk3 and aircrack-ng both uses the osdep-library. I'm not sure if both have 100% "identical" de-auth methods/packets (when analyzed), but it would be interesting to see a packet-capture of the failure compared against the successful one.