Jump to content

Search the Community

Showing results for tags 'fail'.

  • 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 3 results

  1. So I just got my first Wifi Pineapple nano, and followed the firmware update video for android. Eventually I got it to respond to the firmware update. But since I'd ran into issues and reset before, I unplugged it. Only this time it had FINALLY began working on the firmware update(I think). I saw no change in the LED and the only evidence was a phone browser page that failed to load. After this my nano is stuck in a boot loop, so the only way I can get it to stay on and stable is by holding the reset button. I believe this is the recovery mode(total newbie here). The part that has me stumped i
  2. Hi there! I just updated the firmware of my tetra to 2.0.2 and the bug that i've found is still present in here: I realized first in 1.1.2 that "aircrack-ng -J output something.cap" is not working correct. Yes it generates the file, but hashcat can't read the key. This has to be a bug, because when I transfer the .cap file and run that command on two differend pcs, the generated .hccap file can be read successfully in hashcat. Aircrack-ng framework version is always 1.2 rc4. Greetings :)
  3. I have been troubleshooting issues with the bashbunny for as long as it has been available. I got mine as soon as it was released; and it has been nothing but problematic from day one; which is a shame. The device, in theory, is probably the best thing Hak5 has ever come out with; but it practice, it has been the least usable in my experience. Many payloads will not run consistently; if they run properly at all. Every payload that makes use of the USB partition (the one thing that should really allow us to accomplish truly amazing feats) is problematic for many of its customers. The bashbunny
×
×
  • Create New...