Jump to content

The Power Company

Active Members
  • Content Count

    78
  • Joined

  • Last visited

  • Days Won

    2

About The Power Company

  • Rank
    Hak5 Fan ++

Profile Information

  • Location
    Anywhere With Lights
  • Interests
    Zapping

Recent Profile Visitors

947 profile views
  1. Got it, script updated. I don't have my Alfa card on me atm, I'll test whether it works later. EDIT: Just tested it, updated script. It should work fine now.
  2. You right, you right. I changed the script to reflect this change, the old line is commented out just in case
  3. I'm a bit late to the party but I've always viewed the term "hacker" as a sort of title, something bestowed upon you by others. A person can't really decide that they are a hacker, that isn't for them to say. It isn't about what you think of yourself, since that shit is all in your head anyway. It's all mostly about how other people view you. (just my opinion obviously)
  4. Just a heads up, you can get CPEH (Certified Professional Ethical Hacker) and CEH (Certified Ethical Hacker, up to v9) from places like LimeTorrents and The Pirate Bay, their lab exercises are very hands-on and are a great way to expand your knowledge.
  5. Check that your module is actually saved in a directory called /lib/modules/4.15.0-kali2-amd64 (i.e. try to cd into it). The directory may have a different name due to kali updates, in which case you simply must change the directory to the current one.
  6. May sound like a dumb question, but is your pineapple connected to the internet? Either through WiFi client mode or an Ethernet cable? (you can check by trying to load the news on the dashboard or checking for updates)
  7. Really? I thought that hackers were supposed to be as noisy as possible when infiltrating a network!
  8. Is it possible to run Piratebox without OpenWrt? I know the Nano already supports OpenWrt, and I'm pretty sure that the Tetra also does, but it isn't in OpenWrt's Table of Hardware yet... EDIT: I wish I could say that I mean the stock version of OpenWrt, but honestly it was so late what I posted this that I completely forgot that both pineapples already run OpenWrt. I mean its not like it says "with OpenWrt" in the ascii art that appear when you ssh into one... oh wait...
  9. Most laptops don't fit in it, but it is great if you are traveling light (and I mean very light)
  10. I've gotten the web interface working on Ubuntu 17 but I haven't tried configuring it for pineapples yet.
  11. Hey guys, So I have been playing around with the newish web interface for Kismet and it is pretty great. I've just been using the standard wireless cards plugged into USB, however, when Darkmatter did his wifi cactus build, he used a bunch of pineapples connected to one pc using ethernet cables and hubs. Does anyone know if this method of interfacing with pineapples is available to the public yet? And if so, how to do it? I know I could just run Kismet on the pineapple itself, but then I won't get that shiny new web interface...
  12. 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 # used to be: git clone https://github.com/aircrack-ng/rtl8812au git clone https://github.com/gordboy/rtl8812au.git # move into downloaded driver folder cd rtl8812au/ # update files in working tree to match files in the index # this step doesn't seem to be necessary anymore, commented out # git checkout --track remotes/origin/v5.2.20 # make drivers make # move into parent directory cd .. # debugging dkms status # rename file for use with dkms mv rtl8812au/ rtl8812au-5.2.20 # dkms add driver dkms add -m rtl8812au -v 5.2.20 # build drivers dkms build -m rtl8812au -v 5.2.20 # install drivers dkms install -m rtl8812au -v 5.2.20 # debugging lsmod # summon new interface from the depths of the kernel modprobe 8812au # wifi interface should now appear. ip link EDIT 10-17-2018 As per the driver's Github page, added the following line to dkms build steps: dkms add -m rtl8812au -v 5.2.20 Script was successful for Debian, should now work again for any Debian-based linux distro.
  13. Sweet, thanks for the info. You wouldn't happen to know what wlan0-1 is used for, would you?
×
×
  • Create New...