Jump to content

Phobic81

Active Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by Phobic81

  1. On 2/25/2017 at 4:47 PM, stilia.johny said:

    I have the same problem.. 

     

    Tbh on my Tetra is not connecting on both Admin or Open AP. 

     

    I have to reset the network by update the network settings, which eventually will reset the WIFi. 

     

     

    Same here. I can access the ui via open ssid once,  Tried to reset the WPA2 management iface, on reboot /reconnect the open will not auth nor will the management AP accept the password. Strange. My instinct is that I'm using the wrong wlan interface config, or a power issue, or the fact that I'm using a Mac-MacOS. I have the external wlan adapter as well, and wondering if there issue there on power draw. 

  2. Quick question on the Tetra. Set-up stand-alone on with a Management AP running, but trying to start the PinAP fails, On i-face scan only shows wlan1 and warns that using wlan1 interferes w/the PineAP.  The new book recommends adding an external card (have one now), but should I disable the management AP SSID? (must be on Wlan1. (or I'm using Wlan1 for an upstream connection). Sorry, it's early and I'm still waking up. Edit: Basically, the end goal = set up to manage using management by wirelessly logging in, but what would be the most ideal way to assign. An Ethernet cord into a router or switch displays no upstream that I can see. I would think wlan2 (the add-on card) for management, wlan0 - for an upstream net share, and wlan1 for an AP? 

  3. Not sure. Strange. I use Firefox as my primary log in for the web ui. Since the firmware upgrade, I haven't experienced any more glitchy-ness. Maybe using Firefox was causing me the "headaches". So far, it's running fine for me on Mozilla. Post edit: Just set it up on Kali and seems to be running alright on Iceweasel. It didn't recognize the sd (not a class 10 though) card infusions stored on it, until I rebooted it. Tried the new Experimental reformat and it still retained orphaned infusions.

  4. Thanks, 1.3.0 seems to have solved a bit of a bug with Karma I'd been experiencing. Very smooth flash.

    @SixKids "The only thing that displays is the system status message:"

    ​I experienced this too, briefly. and logged out logged back in refreshed two times and it now loads, but I'm using Firefox. Other browsers were buggy for me, as well.

  5. Thanks, it worked out. Somewhat. The 1st sd was corrupted. After formatting in BT5, it was recognized in the Web UI to store infusions. But when downloading to the sd, it freezes. Grabbed a second card from my rubber ducky stash and it does the same. When I reboot the pineapple, it shows the infusions installed to sd. Strange. It might be that I'm using plain micro sd's, so I'll try a class 10 HC and see if it resolves. Things overall a bit buggy. Karma won't enable. Factory reset completes, but still Karma issues. That's an entirely different problem. I've got to get to the root of this. Pun not intended. Happy accident :-)

    Regards,

    Ty

  6. Tried a USB 4GB and partitioning it in EXT4, mkswap command won't execute (just freezes), but "sandisk is shown", never shows option "store to USB" like the MKIV, so it makes sense that USB shouldn't be used. But.. I formatted an 8GB mSD (through the "resources" in the Pineapple UI) and it it won't recognize to storage either. Do I need to do the same here as I did with the USB in the MKIV? Has to be some step I'm missing..

  7. "Phobic81,

    To encode the payload.txt file that you have created just place it in the "/usr/share/simple-ducky" directory and open a terminal window and "cd" to the same directory. Run this command: java -jar encoder.jar -i payload.txt

    As far as importing the wallpaper prank into the simple-ducky, i would perfer not to. The simple-ducky is designed for professional penetration testers and the payloads in the are geared specifically for that purpose. However, I am in the process of completely revamping the simple-ducky. I am going to make it 100% modular, that way plugins can be added by each user. This is going to take some time to complete but it is well worth the effort.

    ~skysploit"

    Thanks. It was the "encoder" that I was missing. Explains why "duckencode®" wouldn't take. Understand keeping it catered to pentesting and I'd prefer to see it at that (primarily because I could monitor my employees, half of whom text more than they work), but we just got this thing and I'm trying to test it out with a simple payload before we try compiling a lengthy custom ducky script. I'll be trying to come up with a payload that executes downloads of default software (Mbam, additional browsers, MSE and UAC setting adjustments, etc) we install on our systems we build for sale. I do more hardware work than anything, unfortunatley. Boring. It's way too time consuming for me, and the ducky might be a faster automated solution, moreso than our junk dvd's. If I can get this to work, then we'll be getting a quite a few of them. Looking forward to the new version. Thanks again.

  8. I've a problem with my ducky. Or probably me. Using simple ducky 1.1.1 on Kali, I'm trying to deploy the simple wallpaper prank on a non uac windows 7 system. Trying to figure out how to convert the payload.txt to inject.bin under the options. Using the java -jar commands on my W7 laptop, it won't recognize duckencode or duckencoder files. When I plugged in the ducky for the first time, nothing happened, then it typed "Quack" etc in the run field. Now it just goes to switch user field. Is there a way to import the Wallpaper prank text using simple-ducky on Kali?Would really appreciate any advice with this. Thanks.

×
×
  • Create New...