Jump to content

vepr

Active Members
  • Content Count

    21
  • Joined

  • Last visited

About vepr

  • Rank
    Hak5 Fan

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm just curious, does "lsusb" show the device?
  2. That is interesting. Something is wrong with my Owl. I've been messing with it for a few hours tonight and discovered that it only works part of the time. It connects to the Wifi AP about 25% of the time. I have several APs that I have tested this on and it won't even connect to some of them. About 50% of the time, the Owl boots up going through the usual LED pattern, then it just goes black and doesn't do anything at all. This is really frustrating.
  3. I also have a Wifi Pineapple and the Packet Squirrel. They do have reset options. The signal Owl seems like it was released too quickly. Maybe they'll provide some updates in the near future. I did have a bad experience with the Keysy RFID cloner though.
  4. Sect10_9 helped me figure it out. My wifi_connect.sh was not in all caps. It should be WIFI_CONNECT.s
  5. ahhhhh I didn't have WIFI_CONNECT.sh in all caps. That did it. Thanks for analyzing that! I'm not using a flash drive for the payload. I have the payloads directly on the Owl device. I checked and it works with both /etc/init.d/sshd start and /etc/init.d/ssh start
  6. Yeah, I'm out of ideas. I have added the #!/bin/bash. I've run the payload with the SSH line commented out. I've also tried using /etc/init.d/ssh and sshd. I wiped everything and copied and pasted the .sh and .txt. Both files are executable. No luck with multiple AP names and passwords. I guess I can try and set a static IP instead of using DHCP.
  7. Yeah, that is strange. I'll try /ssh again. Are you using a USB adapter on the host port of your Owl device? I wasn't sure if I should be trying to connect with the built in wifi or an external wifi adapter. I've tried both. Also, do you keep % on your SSID and Password or do you just have that there to show that it is a user variable? I don't have % but I'm just checking every option. lol
  8. So one method we can get information on the device when connected to a large network is have it reach out to a web server on the internet and relay it's information. Maybe create a simple form and write a script to have the Owl post to that form with it's current IP address and other information. If the network allows SMTP, we could possibly use a Python script that sends an email using Gmail credentials? When I get some time, I can help you guys do this if you want.
  9. That's strange that you have to run /etc/init.d/ssh instead of /etc/init.d/sshd When I'm SSH'd in arming mode, I have to restart SSH using /etc/init.d/sshd restart. Just giving SSH will give me command not found. Does attack mode use a different SSH service?
  10. I can edit the LED settings in my payload and the LEDs run just fine. But when I check my network, the Owl is not connecting in Attack mode. I decided to edit this line in extensions/wifi_connect.sh so that it gives me a log: wpa_supplicant -B -Dnl80211 -i wlan0 -c /tmp/wpa.conf > /root/payload/log.txt The log is telling me that wlan0 is not recognized when booting into Attack mode. I'm using the default settings. Do I need to change it to br-lan in my wifi_connect.sh? my log.txt: Successfully initialized wpa_supplicant Could not read interface wlan0 flags: No such device nl80211: Driver does not support authentication/association or connect commands nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Could not read interface wlan0 flags: No such device wlan0: Failed to initialize driver interface Do I need to use an additional wifi adapter on the USB Host Port? I can plug in one of my adapters with (for example) a Ralink 2870 chipset and my log no longer gives me errors. But it still does not connect to my network via wifi. I have also run the payload using a usb drive and it makes no difference.
  11. I haven't had a chance to check it but the Owl does continue blinking in a pattern I set after turning it on. You can get the Mac address of your Owl with the command "ip a". Then when you boot your payload, you can check your router for connected devices. You can also use the app called Fing to search for your device Mac address. It also allows you to Port scan.
  12. Good thinking. I forgot to do that. It looks like it's working now. Rylore, try chmod +x on the /root/payload/extensions/wifi_connect.sh as well if you haven't already.
  13. I got through the initial setup and set the AP name and password. I can not connect and SSH into the Owl. I"m having trouble with payloads. I copied the example payload and to work in conjunction with the wifi_connect extension. But the device doesn't seem to work with that payload. It goes through the usual blinking, then just stops.
  14. I can't get this payload working. When I plug in the Owl, it goes through all the usual LED blinking cycles. Towards the end it goes through the usual 5 second solid red, blinks fast, slows down, then the LED just cuts off. Has anyone else got this payload running? Should I be able to just plug the Owl in and it will automatically start the payload? I have the payload directly on the device with no USB plugged in. Here are my files. /root/payload/payload.txt: # WiFi Client Setup WIFI_SSID="MYNAME" WIFI_PASS="MYPASS" LED R SUCCESS WIFI_CONNECT # Optionally enable SSH /etc/init.d/sshd start LED R SINGLE /root/payload/extensions/wifi_connect.sh: #!/bin/bash # # Title: WIFI_CONNECT # Description: Simplifies WiFi client mode connection. Expects $WIFI_SSID and $WIFI_PASS # Author: Hak5Darren function WIFI_CONNECT() { ifconfig wlan0 up; sleep 2 echo -e "network={\nssid=\"$WIFI_SSID\"\npsk=\"$WIFI_PASS\"\npriority=1\n}">/tmp/wpa.conf wpa_supplicant -B -Dnl80211 -i wlan0 -c /tmp/wpa.conf while(iwconfig wlan0 | grep Not-Associated); do sleep 1; done udhcpc -i wlan0 } export -f WIFI_CONNECT
  15. I haven't been able to get payload 3 (OpenVPN) working. I have an OpenVPN config and keys that I use on multiple devices with no issues. When I use it with the Packet Squirrel, I get no connection. The OpenVPN server logs show no connection attempts. Below is an example of my config. Does anyone see anything that might cause problems for the Packet Squirrel? The key I'm using doesn't require a password. config.ovpn: client --float dev tun proto tcp remote xxx.xxx.xxx.xxx 443 cipher AES-256-CBC auth SHA256 resolv-retry infinite redirect-gateway def1 nobind # If you turn lzo on, you must have it turned on at the server #comp-lzo yes persist-key persist-tun user nobody group nogroup verb 3 key-direction 1 ca ca.crt cert mycert.crt key mykey.key # TLS auth option so that port scans wont see port is # accepting connections. --tls-auth ta.key 1
×
×
  • Create New...