Jump to content
Hak5 Forums


Popular Content

Showing content with the highest reputation since 07/16/2018 in all areas

  1. 2 points
    No worries ! I worked on this the all day and fixed a few other things here and there. I now have the nat-simple, nat-full and eaponly attacks implemented. Just so that you know, I forked both your hostapd-mana and ManaToolkit repos to keep track of my modifications. All changes are only local on my laptop for the moment but I will keep you updated once it is online. Maybe you will be interested to have a look on the multiple attack scripts. Again, thanks a lot for the heavy lifting work!
  2. 2 points
    Like many others, I bought myself an Alfa AWUS036ACH, only to find its drivers are not set up by default on the latest version of Kali (despite many if its more recent reviews pointing out this fact). I found that there are few guides on how to get this sexy dual-band interface going, so I made a quick shell script to do everything in one shot. A few things to note before we begin: You need an internet connection for this to work This script works great on a fresh installation of the latest version of Kali Linux (2018.1). I tried running the script on a live boot, but the kernel yelled at me when I was modprobe-ing. If you want this to work with live boot, you will probably need to set up persistence or a custom image. Neither of those options are that difficult. Some of the commands towards the end are not necessary for installation, but I used them while I was figuring out how to set everything up, so I left them in there in case anything breaks. If you are anything like me, you may have a few broken drivers polluting your /usr/src folder from previous failed attempts. Delete them before attempting. Once script has run, I recommend you add the following lines to your NetworkManager.conf [keyfile] unmanaged-devices=interface-name:wlan1;interface-name:wlan2 This prevents NetworkManager from trying to resolve the interface using its own stuff when you reboot again (real men keep NetworkManager disabled anyway, but whatever). If your PC already has a wlan0 assigned by default (i.e. is a laptop with built-in wifi), the keyfile above should work fine. Otherwise, just add interface-name:wlan0; before interface-name:wlan1; The reason I also disabled a second, nonexistent wlan2 at the end is because sometimes, if I unplug the interface and replug it into a different USB port, it will be assigned one number up. This measure adds one get-out-of-NetworkManager-free card to your hand, increasing your chance to pass go and collect that sweet $200. 6. Once you have gotten the interface set up, I would recommend using ifconfig to put it into monitor mode, instead of airmon-ng. I've found that airmon-ng tends to have issues with manually installed drivers on occasion. In case you don't know, here is how its done (assuming your Alfa is assigned wlan1): ifconfig wlan1 down iwconfig wlan1 mode monitor ifconfig wlan1 up Anyway, here is the script in question. As you probably already know, you can copy it to a text file called coolfilename.sh, set it to executable, and give that baby a run from the terminal. Or you could always just manually run the following commands one at a time. #!/bin/sh # Shell script to set up drivers for Alfa AWUS036ACH # You must have an internet connection. # update your repositories apt-get update # install dkms if it isn't already apt-get install dkms # change directory to /usr/src cd /usr/src # if you have any other drivers installed,remove them like so: rm -r rtl8812AU-4.3.22/ # get latest driver from github git clone https://github.com/aircrack-ng/rtl8812au # move into downloaded driver folder cd rtl8812au/ # update files in working tree to match files in the index git checkout --track remotes/origin/v4.3.21 # make drivers make # move into parent directory cd .. # debugging dkms status # rename file for use with dkms mv rtl8812au/ rtl8812au-4.3.22 # build drivers dkms build -m rtl8812au -v 4.3.22 # install drivers dkms install -m rtl8812au -v 4.3.22 # debugging lsmod # summon new interface from the depths of the kernel modprobe 8812au # wifi interface should now appear. ip link
  3. 2 points
    If you don't know how to do the above nor how to install / use Kali, then perhaps it's not for you.
  4. 2 points
    Evil Portal 3.1 has been released! Change Log Added ability to write and view logs on a per-portal basis Created method writeLog($message) that writes to the portal log file Created method notify($message) that sends a notification to the web ui Added ability to download files Tab button in file editor will now insert four spaces Revamped the file editor modal Showing file sizes in the portal workbench Various quality of life improvements
  5. 1 point
    off topic but that worked for git, which is what ive had a problem with. working on the same issue with installing .ipk to the nano sd. going to give it a try also. not to great with linux filesystems but been learning the last couple days thank you sir!!
  6. 1 point
  7. 1 point
    Wow, thanks. I completely forgot about that script also messing with the python-dirs. Should be fixed now! 🙂 About the SD-card bug, i actually first noticed it when i was trying to run wifite on my Nano. It would often crash when reading/writing to the sd-card. So it's not just limited to my toolkit, but everything... :S It's just that this crash, and re-naming of the device happens so "fast", so some stuff don't notice it happening. But the kernel would most surely notice it. And i think it's a shame tbh. that this bug hasn't been taken more seriously, considering how many people it's affecting, and some people aren't even aware of it. I've reported everything i've found regarding it to the bug-report site. Some ppl. on Raspberry Pi having the same kernel-version: 3.18.x was having the exact same issue, where they suspected it came from to little power to the device in question. So, i'm wondering if the SD-card is receiving enough juice. If not, then it HAS to be a kernel issue. And i would love to see a jump from 3.18.x to 4.x. I haven't tried installing the 4.x kernel on my devices, even though i've compiled em. But i'm so tempted, just to see if it would fix the problem.
  8. 1 point
    Get a book on Linux first.and start with ubuntu.
  9. 1 point
    Once the wpa3 protocol is actually finalized and released publicly, we'll be able to tell 🙂
  10. 1 point
    Hey everyone, I just wanted to post a quick update to let you know that we have launched firmware version 1.5 for the Bash Bunny. This firmware comes packaged with exciting new features such as a new ATTACKMODE called AUTO_ETHERNET, and a way to send ALT codes using the QUACK command. Find all the fixes and features in the changelog and bounce on by to BashBunny.com/downloads for your devious device download (\_/).
  11. 1 point
    Its obviously not your router, contact the owner of the router/property and ask them for the login details. if they want to let you have them they will. Otherwise ask your other housemates to stop downloading torrents and streaming pron 🙂
  12. 1 point
    No, its position 2 - read the docs 🙂
  13. 1 point
    I have herd that windows can occasionally change IP on you, make sure the IP of the pineapple network is and you have shared to other computers checked. Maybe try Linux 😉 I don't think its an issue with the pineapple itself, maybe wrong but... its always windows lol EDIT - also REMOVE your email, seriously dont make that so public 🙂
  14. 1 point
    do you have your firewall enabled? Ive always had to disable my firewall to get it working on mint.
  15. 1 point
    Thanks for the heads up. I've updated both kismet and kismet-remote. I've built them with the latest versions of libmicrohttpd on my SDK, when the Pineapples are using a much earlier version. I guess this is the reason for your error. I've now built them with the same versions in use on Chaos Calmer. So, should work like a charm 🙂 EDIT: Both kismet and kismet-remote works on my Tetra. But, it isn't factory set, so please report back any issues. :)
  16. 1 point
    OK, please do not take the wrong way. But why would you take a tool on site that you had not vetted yet? While I agree the the PS is a good option for what your trying to do. While you are in the PS can you see the USB drive mounted? Have you tried a small capture without the drive inserted to verify the drive isn't causing some issue? When trying the firmware upgrade, is it connected locally to the laptop/desktop you are using? Have you tried a factory reset to clear everything?
  17. 1 point
    As Rkiver states, unfortunately you won't get much here. Pentesting over the internet, and not LAN/WAN is pretty much guaranteed to be nefarious. If you were pentesting for a company, with signed consent, you'd either be on their LAN/WAN or already have the details of how to attack from externally. Therefore, it's assumed you're trying to pentest someone you shouldn't. So no chicken dinner, sorry.
  18. 1 point
    The symptom does sound like a low power one. have you tried running from a 12V2A supply? to rule it out? EDIT - wait i see you mention you have tried on 12V2A supply and the same is happening... sorry i missed that. I would be inclined to to a firmware recovery making sure i use the special factory firmware file. If the issue is still persisting after that i would contact hak5 official support.
  19. 1 point
    Infinite loops are a bad idea..even an infinite loop based on a variable is better. bRunning="1" while [ $bRunning -eq "1" ]; do # Do your jazz here if [ -f "file" ]; then bRunning="0" fi done # File exists; jazz complete
  20. 1 point
    This was kinda funny lol, Goodluck @ImJustBadAtThings. 😄😀😂
  21. 1 point
    Here was a old video I made 9 years ago. Was a lot of fun. hope you guys enjoy. I won a hackers video contest with this video.
  22. 1 point
    It's also my opinion that you don't need to be very knowledgeable on <topic> to be a hacker. It's a mindset, or a way of thinking, a personality.
  23. 1 point
    MacOSX is the "OS for hackers"? Nah, it's the OS for people who want no control over the hardware that they have no control over. Also not a hacker, at all. I'm a techie. I just work with computers. I would never assume to call myself a hacker, I don't have ANYWHERE near the knowledge.
  24. 1 point
    This has been on my todo list. this is a nice poc. you could go far with something like this. From any device at any time you should always know what's on the network and if any services are exploitable. Automate the shit out of this! I have used meterpreter on my android to pivit exploit code from a remote machine onto a local network... the exploit goes through the tunnel but the shell is directly reverse tcp back to remote desktop. I have also made a reverse proxy to pivot exploit code in the same manner. (Might have some videos) With debian now running In my pocket (android) the possibilities are incredible. My networking kung fu is dangerously scary.
  25. 1 point
    That would be awesome :) I have figured out how to get telnet working on it. 1. Connect the HDD to a linux system and mount the partitions 2. chown file "etc/rc.d/rcS" on 1st partition 3. open file "etc/rc.d/rcS" 4. find the line with content: "allow_telnet=no" and change it to "allow_telnet=yes" (was on line 200 for me) 5. save the file, then set canon station up with the Ethernet port used to connect to router 6. use application to connect to telnet on port 23 with username as "root". no password required. (I used putty on my windows laptop) Hope this helps.