Jump to content


Active Members
  • Content Count

  • Joined

  • Last visited

About tecno

  • Rank

Recent Profile Visitors

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

  1. I got to do a little more testing today and I further discovered that my owl is no longer interacting with the USB port at all. If I press the button while the payload is running, it does not copy any onformation to the USB stick. I can not do a firmware upgrade either, it skips right over the firmware loading sequence and if a script calls for an extension, the owl isn't sourcing the extensions directory. At this point I am sure it is malfunctioning though I don't know if it is software or hardware at this point. If there was a way to reset the device, I could explore further, but at this point I believe I have reached the end of the line. To test if you are having problems wit the Signal Owl interacting with the USB storage you can... 1. Place a payload.txt file on the root directory of a USB flash drive and insert it into the "hot" USB port on the owl. When you boot the owl, the payload file should be copied over automatically and overwrite the existing file if one already exists. 2. Place a file in the /root/loot/ directory on the owl, then reboot. At some point, after the payload is running, press the button once. This should copy the contents of the /root/loot/ directory to the USB Drive. 3. if the above both fail, you could try to flash the firmware as as detailed on the hak5 docs page, but only as a last resort. If any of these steps fail to work properly or in my case, all three do not work, then I can say with confidence the device is not working as intended. tecno
  2. Thanks Merlintime, I suspect you ar right on target with this assessment. After further testing with my owl, I find it isn't sourcing the extension directory at all. Neither is it reading the mounted USB storage for the firmwaree upgrade file. Sadly I suspect some core file corruption or a hardware issue. I'm going to give it one more weekend of testing and see if I can get anywhere with it. Good Luck tcno
  3. Thanks Darren, It's good to know you are working to improve the product and it is really great you are active here on the forums! Thanks man! tecno
  4. Hello fellow signal owl owners... In my earlier post named "SUCCESS! a few simple but effective tips" I outlined how I got my owl to reliably connect to an open network 100% of the time. While that is still true and working, my Signal Owl has started acting very strange and I wanted to share. In the post I mentioned above, I mentioned it is a good idea to start simple and build upon your working script. Well, I took my own advice and tried to add WPA encrypted network support to my owl and failed. Thats not the strange part though, the strange part came when I went to revert to the basic connect script that was just working fine and I lose the ability to SSH in. so here is what happened... 1. copied the known working script to connect to open networks to the owl through the open AP the owl generates at 2. rebooted the owl and it connected to my open network like it should , the IP assigned is, I verified it was so in my router. 3. I try to ssh in and it tells me the host is down, or it just hangs and times out 4. I check to see the payload has the line /etc/init.d/sshd start which it does. This was just working before I tried to connect to a WPA network with the hak5 GitHub script WIFI_CONNECT 5. So I write a little debug line and put it into the script right after the line that starts up the ssh daemon, it looks like this /etc/init.d/sshd start ps -A | grep ssh >/root/loot/debug.txt LED CLEANUP 6. I reboot and the file is there but empty, no output, but the LED is blinking cleanup so the script got to the end and completed all steps. Why won't sshd start up now? I run the startup command for the ssh daemon manually on the command line and check the process list its there, running, so the command works. Now I'm at a loss, the command works but the script will not run it...now what? 7. Next step, reload firmware... right? WRONG! I put the firmware file on the USB Drive, install it into the correct port on the owl, boot the owl, hit the button during selection mode and ........it starts the open AP and never does the upgrade. I've done it 4 times and each time it goes right into the AP mode complete with double blinking LED and all. I can even connect to it and ssh in like usual through curiouser and curiouser... I think it is the lazy techs crutch to blame hardware for a perplexing problem, but in this case.... I am out of ideas and I wonder if any of you are having the same weird issues. Im still reluctant to blame hardware because the behavior is consistent, it is just consistently wrong and odd. Thoughts anyone? Thanks tecno
  5. tecno

    Owl advice

    Hello, Hello, Interesting question, I eventually hope to do some war driving myself with this device however it is very new and version 1.0 so as far as I can tell everyone is still trying to get it to reliably connect and properly work so at this point no one has gotten that far. At least that is, not that I’ve seen post about it. Like I said this is a brand new device just released and I think we are all trying to figure it out however I suspect this is not the correct device to go to war driving with . As you test and discover new capabilities please post and keep us all up-to-date on your progress I’m interested to know how the war driving effort is going… Thanks, tecno
  6. That is supposed to say scoff…I wish I could go back and edit my typos
  7. Hello, Hello, I have been contemplating what to do about the button myself and I have an idea for a solution which I guess would be considered layer 1, You know, a hardware solution. So because these devices are simple and one step above disposable let’s keep the solution super simple as well what do you think of this… Get a small ball bearing or plastic bead the perfect size to fit into the hole where the recessed button is. Now, take one of those artist rubber bands, you know the ones that are extra wide, but the right size to snuggly fit around the device and cover over the ball bearing sitting in the little button hole. Now whenever you want to press the button simply squeeze the area and it will press. When you are finished installing simply remove the rubber band and the button is back to recessed and on able to be pressed by accident which could be a good thing if it’s in a place where you don’t want anyone to disturb it or press the button if someone gets curious. Now before you scarf and laugh at my hillbilly solution, think about it, it is a fool proof Solutions to the problem which will work reliably every time and costs pennies, is easily removed, and can be obtained just about anywhere. Simple and easy… Hope my wacky ideas are helpful Hope my wacky ideas are helpful Tecno So because these devices are simple and one step above disposable let’s keep the solution super simple as well what do you think of this…
  8. Hi, As I was reading your posts above about how to get the IP address assigned so you can later SSH in, and I had an idea. Insed of writing scripts and using a web portal and all that, couldn't you just do this... 1. have your script loaded and ready so you know the Owl will connect to the target network. Have a blank USB Drive handy 2. Once your script is tested and working add a simple line like ifconfig wlan0 > /root/loot/systemIP If you want to get fancy, you could even grep out the IP line and AWK the IP so it is alone in the file, but that's not really neccessary 3. Take that blank USB Drive and insert it into the hot USB port, then click the button. The owl will copy the loot directory to your USB Drive and Whala... simple and uncomplex to minimize failure.. from there your gold. Your already on-site with physical access and this process will take only a few minutes. Alternatively you could have a second flash drive with the production script and have the device loaded with the "recon" script to obtain IP info. Now once you put in the blank drive and get the loot dump, put in the second drive with the production script on it. Once you do, press the button and it will copy the script, overwriting the old one, and restart running the production script and you have the IP and can SSH into it later.This requires no python or HTML or anything and seems more reliable to me. I haven't tested this at all, it is just an idea, so if you see any reason it wouldn't work please post. Hope this helps tecno
  9. Correction to check if you are associated with your open AP and to check if you are assigned an IP, type ifconfig wlan0 and iwconfig wlan0 these commands will show you all the info you need to know about your interface wlan0
  10. As an early adopter of the Signal Owl I like many of you have been a little frustrated with the thin documentation and lack of progress, but after days of testing I have got the owl to reliably connect on its own. Here are a few things that are really important and can help you out if you are stuck. 1. Case is important! the payload must be named in lower case letters to work so your file should be /root/payload/payload.txt NOT /root/payload/PAYLOAD.txt or /root/payload/PAYLOAD.TXT the same applies to your extensions, if they are called as all caps in the payload.txt file like for example "WIFI_CONNECt" , then the filename must be in all caps in the extension directory like this /root/payload/extensions/WIFI_CONNECT.sh 2. Make sure the shebang (#!) starts both the payload script and the extensions. The scripts in the hak5 GitHub are missing the #! at the start, or at least one of them is. Every script or extension should start with this. #!/bin/bash or it will not work at all!!! 3. If you are having trouble getting connected, remove some of the complexity from the equation like this...Lets connect up without the WPA encryption for testing purposes and make it just a little easier. Once the base connection is up and working you can add WPA later. Here is what I did... 1. Setup an open guest network or if your router doesn't support guest networks, turn off the encryption on your router for now. Remember to turn it back on when you are done though! 2. Before booting the owl, plug in the usb Wifi adapter that came with the kit if you bought the kit. When you boot with the USB Wifi adapter installed it bumps the internal Wifi interface to wlan1 and the USB adapter takes over the wlan0 interface designation. Note that the USB Wifi adapter that is now wlan0 starts DOWN. 3. Boot the device and hit the button during selection mode to start ssh and the built in AP on wlan1 4. ssh into the Owl as outlined in the hat5 documentation. 5. Once you have root each of these commands will work if entered into the command line one by one, test them this way and then put them into your script. ifconfig wlan0 up ifconfig wlan0 essid "YOUR GUEST OR OPEN NETWORK NAME" udhcpc -I wlan0 Now you should be both associated with your open access point and have an IP address assigned. To check if it is so, type ifconfig wlan0 and ifconfig wlan0 6. close the connection through plan1 by typing exit and now grab that IP address your router assigned wlan0 and type sudo ssh <ASSIGNED IP address> enter system password when prompted then enter shell password when prompted "hak5owl" and you are in on wlan0. Now you know both adapters are working and you are ready for the script o do it automatically. wlan0 is the interface you will be sting into when the Owl boots up from the script 7. Ok, its time to load the script. here is my exact script which works every time #!/bin/bash ifconfig wlan0 up iwconfig wlan0 essid "Starfleet Guest" udhcpc -i wlan0 sleep 3 /etc/init.d/sshd start LED CLEANUP My guest Wifi network is called "Starfleet Guest" so be sure to insert the name of your own network here. Thats it, it works reliably 100% of the time. Now you have a foundation from which to add other features and abilities such as adding into your script WPA login information or Nmap scanning or whatever... now that your connected the possibilities are excitingly endless!!! Hope this helps tecno
  • Create New...