Jump to content

steps

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

493 profile views

steps's Achievements

Newbie

Newbie (1/14)

  1. Hi everybody! I was reviving three Rubber Duckies today - well, I tried. A while back, I flashed my personal Rubber Ducky to be both an HID and a USB mass storage device. This worked fine at the time and is still performing great. But today I tried to flash two company-owned Rubber Duckies - and failed horribly. I pressed the tiny button on the Rubber Ducky while plugging it in. Here's what I tried so far: 1. Dump the working Rubber Ducky's firmware and flash it to one of the other Duckies: sudo dfu-programmer at32uc3b1256 dump > working-rubber-ducky.hex sudo dfu-programmer at32uc3b1256 reset sudo dfu-programmer at32uc3b1256 erase sudo dfu-programmer at32uc3b1256 flash --suppress-bootloader-mem working-rubber-ducky.hex This was followed by this error message: Error parsing the line. Something went wrong with creating the memory image. 2. Download one of the firmware images from GitHub and try it with them (same commands as in the listing above). I tried several images. That got me the same error. I googled the error message and found articles claiming that this error means that the firmware image is corrupted. Can anyone of you guys please help me figure this out? What I want to do: 1. Flash all three Duckies with the same firmware 2. Find out what firmware I originally used (the one that creates a "hybrid" ducky) Any help on the matter is highly appreciated and I thank you guys in advance.
  2. Hey Foxtrot, thanks a lot for your reply! Let me get trough it step by step here... 1. OK, I was right about how Karma works, good to know :) 2. Hmm, I guess the more recent phones use passive scanning (i.e. waiting for a network's beacon frames) only, at least the ones I have available around here... 3. That makes a lot of sense, but...when I boot up my Pineapple, I immediately get a new WiFi network having the SSID that I put into the "Karma SSID"-field on the Configuration page. Is there any way of disabling this? And what is the sense of this field if the SSID is hidden? I could really use a bit of insight here... 4. That was what I tried over and over again: open an unsecured hotspot, e.g. via a second mobile phone, kill the hotspot and wait for Karma to fake it. That never happened with mobile phones, but I successfully lured a colleagues laptop into connecting to my Pineapple and just finished an nmap-scan of the host :) So to make things short: the pineapple itself works like a charm, but not when using mobile phones. As I am not allowed to use wireshark in my company's network at the moment, I won't be able to verify the lack of probe requests made by the phone until next week, then I'll hopefully be able to give some more details on this issue. I'd appreciate if you could tell me more about the Karma-SSID-field on the Configuration page, as this keeps confusing me a bit (and I'd really love to disable it if possible). Thanks a lot and greets - Steps
  3. Hey everybody! Sadly, my first post in this forum will be a question, as I have a problem with Karma in MK4 (FW 2.8.1). But first of all: I really like the Pineapple, thanks for creating it :) However, here's my problem, hopefully you guys can help me (maybe simply help me understand what went wrong): As I understand it, enabling Karma will put the Pineapple in what I call "Jasager-Mode", i.e. responding to all probe requests with a "yes", thus tricking clients into connecting to it (if they have been connected to an open wifi network). I know that this won't work for secured wifi networks, but only for open ones. When I turn Karma on, I can see quite a lot of probes in the web-frontend's status window and from time to time some poor client even connects to my pineapple. But of course I wanted to try something different and so I decided that it was about time I connected my phone. I asked a colleague of mine to tether my phone to his (using SSID 'example' and no security in Android) and then kill the AP. I then had an AP in my AP list that was (of course) not in range. I then waited for the SSID 'example' to show up in the list of incoming probe requests and for the phone (HTC One, running some custom ROM with Android 4.1.2) to be connected to the Pineapple. But nothing happened. Not a single probe was sent by the phone (or captured by the pineapple). I then tried to change the Karma-SSID to 'example' and the phone found it immediately, connected to it and everything worked as expected. I read somewhere that Android > 4.0.4 does not probe for wifi networks anymore - to test this, I wiped the dust off my old HTC Desire (Android 2.2) and tried the above once more (with the same result). Long story short, here are my questions: Is Karma supposed to do what I think it should do? Is Android really not sending any probes? Why can/must I change the Karma-SSID? Shouldn't it do that automagically? What can I do to trick the Androids into connecting to my Pineapple? I hope I could make my questions clear. Should you need any additional information, please feel free to ask. Thanks in advance! P.S: I tried searching for the solution (in this forum and beyond), but could not find anything useful (except maybe the Android 4.0.4 hint). Should I've missed the answer and thus created a redundant post, I apologize (and would appreciate a link). Greetings from Germany - steps
×
×
  • Create New...