Jump to content


Active Members
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Oli

  1. Somewhere in the order of 500 maximum, 62.5 worst case depending on O/S. Take a look at the bottom of this page: https://www.pjrc.com/teensy/td_keyboard.html Not an exact comparison as the implementations are slightly different, but I guess it is going to be in the same ballpark. It would be interesting to see some benchmarking though if anyone can be bothered.
  2. Yes - kind of - but probably more hassle that it is worth and likely to be many 'gotchas'. You could try some kind of customized firmware, type the exe out character by character, or something like that. Probably easier to just use a second usb and script running / copying the program from there.
  3. Start with a Teensy would be my advice as they are designed for modding :) The duck doesn't have any GPIO available from what I can see so any mods that you can do are going to be fairly trivial. Depending on what you want to do, then an Arduino Leonardo might be a perfect choice and is readily available.
  4. Also, there are likely to be many edge cases - boxes to check, room numbers to enter, email addresses etc so the problem isn't as simple as it first might seem. In the EU you often have to enter a ton of information at the portal and each one is potentially slightly different. Using something like mitmproxy on a laptop to record something that can be replayed on the Pineapple might be a more fruitful / generic approach.
  5. Well post the command that isn't working as expected, your OS and other pertinent information and I'll try and help :) Are you on Windows? Are you familiar with PowerShell? I think the root cause is that the duck / site are aimed more at "script kiddies" and assume the user doesn't want to know / understand what is going on and how the functionality works. A better approach is to devise a script that works for you and then port it into a duck script rather that using a site to auto-magically generate a script... The unreadable / hard to maintain scripts are the reason that I don't use the duck anymore (along with accidentally breaking my duck when drunk! :) )
  6. You are preaching to the choir :) Arduino is great, but what we need is a compelling use case - something awesome that can be done with it using the Pineapple. I think there are some compelling stuff you could potentially do - displaying harvested passwords, displaying connection attempts, tactile switches to launch specific attacks, multi-color LEDs that display the stage or success of attacks, etc etc. I guess making a pineapple "headless" and not needing a PC/phone for standard use. Do I think the HDK as it stands is great for that? Do I think the software component of the HDK will be good enough? Not really to be honest and I have left the Pineapple eco-system as there is a lot I don't like about it, although I hope that somebody does do something cool with it. A year ago I would have bought a dozen and tried some stuff out, but nowadays I'd rather build something bespoke and not so compromised as the current offering. The price point of $12 does seem pretty good though.
  7. Well at what point is it failing? The ducky isn't doing anything magic - it is just a keyboard typing faster than a human can. I suggest you work out how to do the report by hand and find out what needs to be executed on the keyboard. Unless you provide a fail case or more information nobody can really help you...
  8. Not sure what you are actually meaning here... The pineapple pins are as I originally expected / reverse engineered. The new HDK headers / pins are just normal arduino pins as labelled on the silkscreen. The HDK enables the Pineapple to communicate with the Arduino board over SPI and in fact wastes an opportunity to utilize many of the GPIO pins. Arduino is pretty cool but a compelling use case is still needed. You can easily add displays etc but you still need lots of "glue" code on the pineapple do to anything meaningful. Arduino does nothing in terms of RAM/CPU, however you can offload some tasks (for example display logic, neopixel timing etc) to stop the Pineapple getting too bogged down. You can in fact add leds, dips etc without even needing Arduino.
  9. Perhaps look at the actual script and just do the actions manually to see what is going on?
  10. I wouldn't bother just yet as the github is never updated... For code contributions to work properly, a meaningful infrastructure needs to be in place. https://github.com/WiFiPineapple/MK5_Interface Excluding the infusions, the code might as well be closed source.
  11. Just to be pedantic with respect to the GPL, actual source and not diffs should have been provided (or an offer to provide them made)... http://www.gnu.org/licenses/gpl-faq.html#DistributingSourceIsInconvenient
  12. 5v would maybe work ok, although you might not get a full 5v on the usb ports. Give it a try, if you have issues swap it for 12v although this will dissipate more heat.
  13. If you can do it with a keyboard then you can do it with a duck. It is not a magic exe execution device. In your case you would have to know the password etc etc.
  14. I think you have any pretty much missed the point of the BadUSB here. 3 above is rubbish, teensy blows the duck out of the water on every level bar the form factor / connector. For traditional duck functionality I would go for teensy as a first choice and a duck if you are a newb.
  15. Give a man a fish and you feed him for a day; teach a man to fish and you feed him for a lifetime..
  16. Just google for OpenWRT lease time and that should provide some relevant information.
  17. No point. It is pretty low capacity and not as convenient as an SD card that you can pop out and use in a PC with an adapter. It is essentially EEPROM without the low number of write cycles. So you *could* use it in a peensy device (not a ducky as that has no suitable I/O), but exactly why you would want to when it has low storage capacity and disk access isn't a bottleneck I don't know. There could be some corner cases where you would want to use it, such as when the built in microcontroller EEPROM is too small and you want to store a payload or something without adding an SD card - but typically in that case I'd use an external EEPROM as they are cheap as chips
  18. Good stuff. Must have been some cold joints with the soldering / continuity problems.
  19. How are you testing? The dipstatus infusion? I'd be tempted to be using something like that to debug what is going on. I've given up on my pineapple and have some spare switches laying around so I might crack out my soldering iron and see if I can get it to work. I can't think of anything that could be causing issues. You are just using a standard toggle with no additional circuitry right?
  20. In this pic: https://www.dropbox.com/s/w5d36trcnzweq1y/20141118_094452.jpg?dl=0 The DIP is on and therefore the wire is redundant.
  21. That should work.... The DIP switches are normally open. So, make sure that all switches are up (i.e. in the off position) for operation with the external switches - one picture has a switch down, along with the wire attached. What I'd do is check the soldering is all good. With a multimeter and all switches up/off ensure no continuity between the corresponding IC socket pins. Next put all switches on/down and check that you do have continuity between corresponding socket pins, Also remember that some pins have crazy non-user user customizable uses, so make sure that if you are connecting your switches that they are definitely open (i.e. not on) for normal use,
  22. Should be an easy swap out. Desolder DIP switch and add wires to a SPST switch (or correctly wire up a another kind of switch). I guess you may have wired up a switch wrong or it may be the wrong way around - i.e. what you think is ON for the switch is actually OFF. Do you have some pictures so I can take a look?
  23. Nice little hardware hack! Yep, could definitely do with a bit of soldering practice (and much less solder) - I recommend the eevblog videos. Also could do with less insulation being stripped from the wires to reduce possibility of shorts/etc.
  24. You do need a delay for drivers. The ducky doesn't know if drivers are installed and good to go - it just blindly fires off the keystrokes as programmed.
  25. This thread contains pretty much everything since then. Still no sign of a final hardware product in the hakshop or any software support.
  • Create New...