Jump to content
Hak5 Forums

Search the Community

Showing results for tags 'led'.



More search options

  • 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
  • WiFi Pineapple
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • WiFi Pineapple Mark V
    • WiFi Pineapple Mark IV
    • Pineapple Modules
    • WiFi Pineapple University
    • WiFi Pineapples Mark I, II, III
  • Hak5 Gear
    • Bash Bunny
    • Packet Squirrel
    • LAN Turtle
    • USB Rubber Ducky
  • Hak5 Shows
    • Hak5
    • HakTip
    • Metasploit Minute
    • Threatwire
  • Community
    • Forums and Wiki
    • #Hak5
  • Projects
    • SDR - Software Defined Radio
    • Community Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Found 9 results

  1. How to get Police LED

    Hi how do i get the police led sequence from the update flashes I want to implement this sequence into my payload, whats the code I need to write to get the sequence and how do I change the colours and the timing. Changing the colours and timing is just changing values but I don,t know how to recreate the police lighting. Thanks
  2. TwoTone LED

    So I have tried a couple things and I only get a white LED from my arming mode payload. LED W B 500 <---- only shows solid white LED W B SINGLE <----- only blinks white I want the LED to blink blue and white similar to the update RED and BLUE but slower blinking. Anybody got some advice on this
  3. Solid amber light

    I have a solid amber light on my mark 5 after installing the 2.4 bin file through the GUI on 192.168.1.1 after powering up while holding the button and continuing to hold for 10 earth seconds. really would like to get my pineapple running again.. -Jon
  4. LED Control

    I've only had the BB for a few days so please excuse me if I'm asking a stupid question. How do I turn off the LED? on ver 1.0 of the firmware it seems to have been LED with no parameter, but this does seem to be the case in ver 1.1. I can pick most of it up from other payloads, but is the any documentation on controlling the LED.
  5. When connecting my nano to my windows machine, the led turns on for about 3 seconds and turns off. The GUI is unreachable at 172.16.42.1:1471. When trying Darren's recovery method where you set a static ip in the 192.168.1.X range, I reconnect the nano while holding the reset button and get a solid LED, but when going to 192.168.1.1 I am redirected to the Asus web management of my router instead of the recovery page. Any help would be appreciated. Thanks :)
  6. BashBunny Leds issue

    Okay. So I just got my bash bunny today and the LED lights were working a when I got it (amber, yellow, purple, blue) But now the payloads "run" and the only led light that works is Green for when I plug it in arming mode. It will not turn other colors.
  7. tl;dr- Add logic to the RD to monitor key lock values. Use this for functions like file transfer. Because I wanted to see if I could, I wrote a VBScript to transmit a file using the Scroll lock, Caps lock, and Num lock keys. As it turns out, if you record the data with a fast enough camera you can decode the bits and reproduce the transmitted file. Unfortunately, to make it feasible for a camera to pickup the LED fluctuations and and then for a human to interpret the blinks, the transfer rate is very slow. In fact, if you have the time and ability to use a camera to record the computer, you should really just take a picture of the screen. If only there was a technical means of monitoring these LED statuses that could increase the rate at which this could operate... (Note: In the above video, you have to view at 60fps and set the playback speed to 25% to even have a chance of decoding it manually) Fast forward a couple days and I saw another demonstration of the Rubber Ducky on Hak5. As I understand it, the RD interprets a compiled script and primarily acts as an output only HID. Because of this, payloads from the RD have only two ways of currently gathering information. One is to exfiltrate the data over a network connection (bad because it may be logged by a firewall or proxy), and the other is to switch to USB storage mode (bad because systems may monitor or block USB Mass Storage Devices). However, by utilizing Caps/Num/Scroll lock, payloads could potentially communicate any type of data back to the Rubber Ducky (without tripping any host system security/monitoring). I'm suggesting that some logic be added to the RD to monitor the Key Locks and use them as a way of receiving data. In the video demonstration demonstration, I used sendkeys to flip the status on the three LEDs. Every-other-bit is sent to Num Lock and Caps Lock with Num Lock being bit one, Caps Lock being bit two, and Scroll Lock always being the timing. For efficiency's sake, every transmission of two bits is indicate by alternating Scroll Lock. This means that with SL turns on, two bits were sent and when SL turns off, 2 more bits were sent. This timing is necessary to indicate to the interpreter (be it human or RD) that the other two bits are current (even if they haven't changed in value). The script currently lacks any intelligence- it just blindly sends the contents of a file. But, if the script were to know it was talking to the RD, it could wait for acknowledgements from the RD before sending a file. Furthermore, since this technique would allow two-way communications with the RD, we could incorporate useful file transfer features like CRCs and the inclusion of the file name. As I mentioned in the beginning, using this technique to visually send information via the LEDs is too slow to really be of any value. But, this same technique may have value when the thing observing the LED value changes is a Rubber Ducky. I estimate that this technique would allow binary data to be sent to the RD at around 1.5 kB/s. Granted, this is a far cry from USB Mass Storage Device speeds and network transfer speeds, but this method doesn't require a system to be on-line and wouldn't leave any trail on the host system*. Of course, in addition to file transfers, two-way communications with the RD can open up more possibilities. For instance, the RD could run a script on the host system to see what version of the OS is running and then send the OS version back to the RD. From there, the RD could send a different script based on the version. Granted, you could just put this logic in one payload file that is executed on the host, but there may be cases where you want to keep some secret sauce on the RD and never written to a host machine. The Duck Whisper *- Okay, some key-loggers might record the key presses. But if the system has a key-logger, it would have recorded the entire RD session anyway.
  8. Hi guys! This is a module for the NANO and TETRA that allows you to configure the LEDs on the device to have different behaviour, through the use of various kmods. It will allow you to use timer, netdev, heartbeat etc as triggers, as well as the ability to toggle each LED on and off. Cheers, Foxtrot
  9. Hidden Green LED

    Hi, So while digging around the NANO I discovered two LED devices labelled "ath9k-phy0" and "ath9k_htc-phy1". The first one isn't too interesting, but the latter, "ath9k_htc-phy1" is the device entry for a green LED on the NANO. Go ahead and look through the cutout for the female USB port, you should see it lit up. I think these LEDs were left in by accident by the manufacturer for the second radio. And while it is pretty useless because you can't see the LED easily, you can control it. If you'd like to mess with it, I recommend reading this and experimenting with different triggers. To enable a simple blinking of the LED, edit "/etc/config/system" and place the following underneath the existing led config block. config led option name 'wlan1' option sysfs 'ath9k_htc-phy1' option trigger 'timer' option delayon '5000' option delayoff '2000' Your config should then look a little like this: config system option hostname Pineapple option timezone UTC config led option name 'wlan0' option sysfs 'pineapple:blue:system' option trigger 'netdev' option dev 'wlan0' option mode 'link tx rx' config led option name 'wlan1' option sysfs 'ath9k_htc-phy1' option trigger 'timer' option delayon '5000' option delayoff '2000' config 'timeserver' 'ntp' list 'server' '0.openwrt.pool.ntp.org' list 'server' '1.openwrt.pool.ntp.org' list 'server' '2.openwrt.pool.ntp.org' list 'server' '3.openwrt.pool.ntp.org' option enable_server 0 -Foxtrot
×