Jump to content


Active Members
  • Posts

  • Joined

  • Last visited

Everything posted by Merlintime

  1. I do not claim to be an expert in the Signal Owl, Linux, scripting, etc; but hope that someone will be able to find this information helpful. There are multiple ways to accomplish some tasks. The commands listed below are what I used to get my Signal Owl up and running with a simple payload (first one was WiFi Connect). First, I highly recommend everyone check out Darren's Signal Owl - Getting Started video. It's very helpful to understand the Signal Owl setup and most important (for me) the LED sequence and when to push the button for Arming Mode. I've seen several posts which indicate their Signal Owl does not copy payloads/extensions from a USB Drive. Currently my Signal Owl is behaving in a similar fashion. I'm using a FAT32 formatted drive with the payload in the root of the drive but so far, no success. My Workaround: Manually copy the file from the USB drive to correct location on the Signal Owl (/root/payload). Steps: 1. Power on the Signal Owl. 2. Push the button during Select Mode (Red fast blinking) 3. Connect your device (compute, phone, etc) to the Owl_xxxx Access Point 4. Connect to Signal Owl ( via Putty (or some other SSH terminal utility) as the root account. 5. type: df -h (This should list the volumes mounted by the Signal Owl. My USB drive was /mnt/sda1). 6. type: cd /mnt/sda1 7. type: ls -l (if you want to list the files in the directory) 8. type: cp <payload file name> /root/payload 9. type: cp extensions/<filename> /root/payload/extensions (Optional: Only if extensions need to be copied also) 10. type: cd /root/payload 11. type: ls -l (if you want to list the files in the directory) 12. Verify the payload file has execute permissions (At least for the owner). If not, type: chmod 744 <payload file name> 13. type: cd /root/payload/extensions 14. type: ls -l (if you want to list the files in the directory) 15. Verify the extension file has execute permissions (At least for the owner). If not, type: chmod 744 <extension file name> Personally, I check a couple times to make sure I've updated everything correctly. That will be up to you. At this point, you should be ready to test the payload. Power off the Signal Owl, ( I count to 10) then power on the Signal Owl and watch the boot process. Depending on the payload, the LED should indicate when the payload has been successfully executed. Alternate Transfer Method: An alternate method to copy files from your system is to use (if using a Windows OS) the Putty utility PSCP or PSFTP. Linux should have those SCP or SFTP already loaded. Once the files have been transferred to the Signal Owl, I recommend verifying the file(s) have the correct permissions for execution. Rotating Payloads: Personally I prefer to not constantly copy files to and from the device when which switching payloads. I connect to the Signal Owl and rename payloads not in use. Which ever payload I want to be active is renamed to payload.txt (or payload.sh or payload.py; whichever fits best). Example: WiFi Connect: /root/payload/payload.txt is renamed to /root/payload/payload.txt_wifi_connect Garbage SSID: /root/payload/payload.txt is renamed to /root/payload/payload.txt_garbage_spammer Extending USB Ports: I used a Anker USB 4-port hub (plugged into the USB 2.0 port on the Signal Owl) to extend the available USB ports. This allowed me to have an additional WiFi adapter (RT5370) and a USB Drive connected to the Signal Owl simultaneously. In the future, I'm hoping to test running an extra WiFi adapter and a GPS module from the USB hub connected to the Signal Owl.
  2. I've not had any luck with the Signal Owl mounting a USB drive since following the initial setup instructions. To get payloads in place, I've been using the PSFTP utility to connect to the Owl. This method isn't likely going to help you since need to re-flash the firmware. Plan to test out the USB drive more this weekend. Keep the info coming so we can continue to learn from each other. 🙂
  3. I find that it wasn't necessary to have the /root/payload/extensions/wifi_connect.sh file rename to WIFI_CONNECT.sh. This file creates a WIFI_CONNECT function and exports this function for the payload during the session. For me, a key step was making the following files executable. /root/payload/payload.txt /root/payload/extensions/wifi_connect.sh <-- Used with the WiFi-Connect payload On a slightly different note, I also found the USB port would extend to a USB hub which should allow additional devices (SDR, GPS, etc) to be connected. You provided good information which helped point me in the right direction to get the Signal Owl up and running with a simple payload. I also recommend people check out Darren's Tutorial Video to help explain the LED sequences. I noticed the video after spending a little too much time figuring out the sequences to get into arming mode. Looking forward to some awesome payloads the community develops.
  4. I made a mistake when posting my comment. I would seem I probably shouldn't post with it's nearly 1AM. ? When gathering SSIDs for the pool I use the 'Deny' filter (I originally stated 'Allow'). My 'Deny' filter is usually empty which allows the Pineapple to add any new SSIDs. encountered.
  5. If you are attempting to add SSIDs to the pool, the filter needs to be set to 'Deny'. If set to 'Allow', only SSIDs with matching MAC Addresses will be allowed to connect, this would include adding the SSID pool. At least that's my understanding of how it should work. I have mine set to 'Deny' when gathering SSIDs for the pool which has been working fine. WiFi Pineapple Wiki
  6. It would probably help to have a bit more information. What OS are you using? IP Address of the client from which you are attempting to connect to the Pineapple? Which web browser are you using? etc....
  7. There a several videos in the WiFi Pineapple University along with the WiFi Pineapple WiKi which may be helpful. Additionally, there's the WiFi Pineapple booklet (a printed version should have been included with your Pineapple) which information about Internet Connection Sharing configuration.
  8. Shmigsy, Since you are using a Windows PC, perhaps this video will be helpful. Windows Internet Connection Sharing - WiFi Pineapple Mark V - Pineapple University Additionally, it may be better to work with the Pineapple in stages to gain more familiarity with it's functionality and how WiFi functions. Sample Stages: Stage 1 - Connect via Ethernet. Navigate WiFi Pineapple interfaces to become familiar with the stock functionality. Stage 2 - Connect via Ethernet. Configure Windows to share Internet access with WiFi Pineapple. Use a device from WiFi lab (laptop, iPod, tablet, etc) to connect to the default SSID. Verify Internet access. Stage 3 - Connect via Ethernet. Configure Windows to share Internet access with WiFi Pineapple. Enable Karma. Use a device from WiFi lab (laptop, iPod, tablet, etc) to connect to the 'karma'd' SSID. Verify Internet access. Stage 4 - Connect via Ethernet. Configure WiFi Pineapple to connect to an AP for Internet access. ETC The above are just examples. It's really up to you based on your level of experience (WiFi, Linux, Windows, etc). If you are less experienced, it may be better to take it slow and go through the WiFI Pineapple University videos, Tutorials on the forums, forum threads, etc. I personally use a small NetBook loaded with Kali Linux in my WiFi lab environment. The wp5.sh script is quick and easy and haven't had an issue having the NetBook connected to the WiFi Pineapple via Ethernet and the Pineapple connected to an AP. Clients who connect to the Pineapple are able to access the Internet and I can still access the Pineapple management page from the NetBook. Helpful Links: WiFi Pineapple University WiFi Pineapple WiKi
  9. Successfully updated last night. Wasn't able to get the update through the web interface but the manual instructions worked perfectly. Looks like a great update and looking forward to working with the new features! Thumbs up!! :)
  10. I picked up a SanDisk Ultra 32GB MicroSDHC Class 10 UHS Memory Card for use with the Pineapple. So far it was working great.
  11. In my opinion, It would be best to get permission in writing before doing anything.
  12. The WiFi Manager infusion should be able to help by providing additional options to manage WiFi (choose to broadcast or hide SSID, AP or client, etc). Once you have the infusion installed, it should show up as a tile on the WiFi Pineapple management page.
  13. Sounds like it may be a routing issue. What flavor of Linux are you using? What is the result of the 'route' command?
  14. I've gotten the red light when I forgot to put the SC card into the Ducky. Assuming you've attempted to adjust the SD card?
  15. PowerShell scripts end with a .PS1 extension. The PowerShell ISE editor is normally the default editor but I imagine you can use your editor of choice. I don't believe the code would need to be run through Visual Studio.
  16. Having those infusions available to the WiFi Pineapple community does not cause the device to lose it's credibility (in my opinion). Many of the infusion are made by members of the Pineapple community and allows us to use the Pineapple however we wish. If your desire is to use the WiFi Pineapple solely as a WiFi pen-testing tool, then by all means do not install the undesired infusions. That's the beauty of a community developing and supporting infusions and the freedom of choice. Pen-testing tool or educational tool, it's up to the owner. I'm enjoying working with my education toy. :)
  17. I'm am by no means a PowerShell expert, just starting to work with it actually. I've used VBScript heavily in the past but PowerShell appears to be much better to work with. Below is an example of a script which can pull PC information remotely. I imagine the script can be modified to pull the information you are looking for and to take it's input (the computers from which you want to pull the information) from a file. An output file can be generated for each PC (if you want). http://gallery.technet.microsoft.com/scriptcenter/2a8a008c-ee30-4b50-a81a-1b7545ef3436 Anything that I could automate with a script made my life much easier (especially if this task will need to be performed periodically). The link below has some tutorials to get familiar with PowerShell. http://www.powershellpro.com/powershell-tutorial-introduction/
  18. Are these systems networked? If you have 200 systems, it may be better to utilize PowerShell to reach out remotely to pull the information? That would save you the effort of walking to each system and putting your Ducky in each system.
  19. Yes, you are correct. The screenshots show the wp5.sh script running successfully in a virtual Kali instance running within VMware Fusion with the Mac OS as the host operating system.
  20. I'm not familiar with Mac OS X. I believe the wp5.sh is for a Linux OS. The link below May help with setting up for the Mac.http://wiki.wifipineapple.com/index.php/Internet_Connection_Sharing#OSX_with_VMware_Fusion
  21. You are running the script with an admin account (or using sudo)?Have you tried to pull down another copy of the wp5.sh script?
  22. Is the gateway being properly set via the wp5.sh script?
  23. I believe the AR9331 is WLAN0 (blue LED) and the RTL8187 is WLAN1 (red LED). Edit - mw3demo, Didn't see your response before hitting the submit button. :)
  24. Hey Sebkinne, Pulled down the update and the tab works perfectly! Thanks for the quick response. With the Karma clients getting, I guess 'kicked' isn't really the proper way to explain it. Previously when I stopped Karma, the clients would disconnect. I assumed the clients disconnected since the faked AP no longer existed once Karma was stopped. Should the client(s) remained connected once Karma has been turned off?
  • Create New...