Jump to content

Zylla

Dedicated Members
  • Posts

    647
  • Joined

  • Last visited

  • Days Won

    46

Everything posted by Zylla

  1. RT @vanhoefm: Inside the Atheros Wifi chips by Adrian Chadd, 2014 https://t.co/qOI0FfWtnj < He's the main force behind open sourcing ath9k_…

  2. @hak5darren I’d love to be there!??

  3. RT @FruityWifi: FruityC2 en Ekolabs 2017! Viernes 29 Septiembre, 11:00 - 13:30 hs. Post-exploitation framework based on the deployment of a…

  4. RT @GossiTheDog: Don't worry guys, Equifax is also a root CA to verify HTTPs on basically every device on the internet. https://t.co/DvtsBO…

  5. @MayedAhmed_ @cryptolok Directory Traversal in it self is defined as an attack vector, so yeah.

  6. I'd be very interested to see your notes, as i've been thinking about this for a while. :) I actually downloaded gps2ip a while back, but i never really got around to testing it really thoroughly.
  7. Success! I managed to compile it myself, after some evening-tinkering. I've uploaded the OpenWRT-SDK Makefile and the IPK-file to my GitHub-repo: https://github.com/adde88/reaver-1.6.1-openwrt/raw/master/bin/ar71xx/packages/base/reaver_1.6.1-1_ar71xx.ipk Haven't tested it yet on my Pineapples, but i don't see any reasons for why it wouldn't work ;)
  8. I'm already working on the new Reaver. ;) BUT: It requires some special workarounds to get it to compile for these devices, which the devs. had made available for the previous versions of Reaver. (Big_endian branch on GitHub) This new version will not compile out of the box. So someone either needs to make it themselves, or the devs. has to bump the Big_endian branch to version 1.6b. Sadly the Big_endian repository hasn't been updated since two years ago. That being said: I will post it to these forums the moment i have it compiled for you guys :) EDIT: A request for a version bump on the Big_endian branch has been posted to the Reaver GitHub repo. Perhaps if people could post comments supporting my request it will get more attention? Here's the link to my post: https://github.com/t6x/reaver-wps-fork-t6x/issues/161
  9. The cause could be that the binaries you're running (reaver, wash, bully) is built with the earlier version of libpcap. When we're sym-linking we're tricking the Pineapple into thinking it's the correct version. But that version will probably have some different symbols, functions etc. compared to the earlier version. When the binary then tries to execute something from the library that doesn't exist, or is renamed, or revamped it will seg-fault. If i remember correctly there should be some versions of reaver in this thread uploaded to mega that is compiled with the new libpcap. You could try installing them and see if it fixes the seg-faults.
  10. You need to provide more details if you want help. For instance: Did you follow the instructions? If you did, it should work. On both the Tetra and the Nano. Did you do the sym-linking that was mentioned in the guide? Also, what error-messages are displayed when trying to run reaver/wash after upgrading libpcap to v1.8?
  11. 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.
  12. 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.
  13. Are you able to test injection on another access-point? It even works against my phones wireless ICS.
  14. I'm having no issues when i'm de-authing, both on 2.4GHz and 5GHz. Never had.
  15. I didn't have time for a diff, so i just upladed the entire module as an archive. Recon_TETRA.rar
  16. I can very much recommend the Tetra, it's still going to be viable a few more years. Good CPU. Enough RAM, and plenty of flash storage. :) i guess the next gen. is going to get an upgrade on the cpu, ram and the wifi chips. I'd be interested to see the performance comparison when having lots of clients, while intercepting/manipulating SSL-traffic if they tested a quad-core ARM CPU with at least 1GB RAM. :)
  17. You guys that need a fix while waiting for a new firmware-version can take a look at this thread. I provided an installation-package (IPK) file for the Pineapples, which will upgrade the version of libpcap from 1.5 -> 1.8.1, thus solving the problem. Follow the instructions in the thread, and you'll get full functionality of Reaver, Wash, and everything else. :)
  18. I use Sublime Text 3, and i've also had good experience with using Notepad++. Both have SFTP plugins you can use to make changes directly to the Pineapples, so that changes happens instantly. By the way, Sebkinne: Do you have any tips for plugins except SFTP that are useful for this sort of development?
  19. Yeah i'm running LEDE, and i'm using some of the source-codes provided there to keep some stuff up to-date. It looks like LEDE and OpenWRT could carry on like "two branches of the same thing". If you ask me, LEDE is the basicly the same as OpenWRT, just a newer version. As i've understood; some of the devs. at OpenWRT left because of: "reasons", and they started up the LEDE-project. I've also understood that they share some of the work they do with OpenWRT, and back again. So, i'm not sure what's going to happen in the end. LEDE is working great in my opinion :)
  20. You could try using reghack2, to see if you get access to all these channels. It removes some regulatory limitations that are set within two kernel-modules (cfg80211.ko and ath.ko) If you're unable to find a IPK to install it, pm me. :) PS. Might be a good idea to test these commands, before and after, to check if anything gets affected there. iw reg get iw phy0 info
  21. I felt the need to say that this is somewhat wrong. Both are used for sending/recieving. When using wlan0 to broadcast, you also need to be able to recieve packets. If you are broadcasting a fake AP 2000 meters, you would not be able to see any probe-requests from the clients that are 2000 meters away, because their antennas can only transmit that far. If they all had a Yagi pointed towards you, then it'd be fine and dandy. This is why i mostly use Yagi's on both the client and the AP, to transmit a AP far away. Or you could probably use it together with some parts of mdk3, as a "sniper-rifle". On the Pineapples i prefer using a strong omni-directional antenna. (+8 dBi or more)
  22. I don't have any issues with Win10 Creator Update, and i'm using ICS just fine. Same when using wp6.sh on Ubuntu and Kali. Also works under VMware. When having the Nano connected, do you have any drivers that are not installed? Do the computer recognize the network-device when you connect the Nano over USB? It should appear in "Network and Sharing Center" under "Change adapter settings." That adapter should have the IP: "172.16.42.42" specified manually. And then your "WAN" network-adapter should be shared towards your Nano-connection.
  23. I have not used or tested Certbot, i've just taken a quick glance at it. If it's a collection of bash scripts that interacts with python and openssl, then yes, in theory it should work. But if it ever needs/uses software compiled specifically for computers (x86/x64 CPU's), then NO. You would then need it compiled for these embedded devices (MIPS).
  24. Yeah that's definitely PineAP's work. Kinda ironic, your Pineapple falls victim to itself when trying to connect to a AP. =)
  25. If you've built a kernel you could try replacing your current kernel by using opkg. Be mindful that you also need to build all the kernel-modules that is used by the Pineapples. If you've built everything correctly, it should work like a charm. Or even better: Build a complete firmware-file, and install it using sysupgrade. (I know the Tetra launches the kernel from the bootloader, before getting your rootfs up. So opkg-intallation might not work that great there. But you should know how to un-brick it, in case anything goes wrong, before attempting a firmware install.) To get a list of all the kernel-modules needed on a Pineapple with all the modules downloaded, use this command below: opkg list | grep kmod- | awk '{ print $1}'
×
×
  • Create New...