no42

Depends on VID PID, has the driver been loaded before, what OS, current processor load on OS. Something out of our control. Driver installation bypass, is only if you mimic the VID PID of a previously connected and valid device.

you could read up on http://www.akadia.com/services/windows_registry.html

? What version of the Encoder? and we need to see the full error message.

Thanks for this, I committed changes to the v2 branch.

Think of all the possibilities...

This is achievable on the manual firmware Hard-Code . Looking at the Encoder source, this combo has not been implemented. You can either implement this feature yourself and send me the patch, or patiently wait.... when I have the time I'll look into it and implement it.

"Command space" should work... strange, I just tried it on Mavericks?

try: GUI KEYPAD_PLUS

some three-key-combos don't work, think this is an encoder issue. I've attempted to patch encoder.java in the svn (https://code.google.com/p/ducky-decode/source/browse/trunk/Encoder/v2/src/Encoder.java) If you would like to test it? Not sure if its working right as I don't know the proper packet sequence - I guessed.

you mean https://wifipineapple.com/?source

http://en.wikipedia.org/wiki/Master_boot_record http://technet.microsoft.com/en-us/library/cc976786.aspx http://starman.vertcomp.com/asm/mbr/STDMBR.htm http://www.bydavy.com/2012/01/lets-decrypt-a-master-boot-record/

This module has been tested successfully on IE6 - IE10, Windows XP SP3 / Windows 7 SP1 on both x32 and x64 architectures. Does your architecture fit these requirements?

CVE-2013-0074 appears to be in Metasploit, get your r00t on: http://www.exploit-db.com/exploits/29858/ This particular exploit should only run on the following versions: 4.0.50401 4.0.60310 4.1.10329 5.0.61118 5.1.10411

At the end of 2012, our aim was to implement the Hacker Zodiac with 2013 starting with the year of the Duck! The USB Rubber Ducky (aka Ducky) has seen some important advancements due to the tremendous support from the Hak5 community. A brief summary: The Ducky now supports BOOT MODE and should work if the BIOS supports USB Keyboards Anti-Virus / Device Management Evasion Additional language key-mapping support (still ongoing...) Improved Ducky Encoder Additional and Fun Payloads spanning various Operating Systems: WinXX, Linux, OSX, BSD, Solaris Lots of bug fixing Lots of source code released Additional Frameworks eg. Simple-Duck-Payload-Generator, DuckToolkit :D Most importantly - a BIGGER community. Just wanted to send my thanks out to the community for such a great year; for all your feedback, and help generating new language key-maps - without you this would not be possible? Wishing you a Happy 2014 and keep on Ducking!!! PS: For all those new Duck owners you might be interested in https://forums.hak5.org/index.php?/topic/28627-info-how-i-wrote-the-community-edition-firmware/ , I am hoping this will inspire you to pick up the code, and further the development of this cool device - you never know I might have missed something, and you'll generate even cooler firmwares compared to the code I've already developed. (Think 2014 might be year of the Pineapple ;) )

also check out the links in my signature...

It will only run the script while connected. Unless your ducky script creates a batch file (*.bat), in which case you should be able to unplug the duck - once the batch-file is executed!

Try: DELAY 3000 COMMAND SPACE DELAY 500 STRING textedit DELAY 500 ENTER DELAY 750 STRING Hello World!!! ENTER

Yes, but the leds are handy for diagnosing potential problems. If you want to turn them off; use the source!

You could help with this: https://code.google.com/p/ducky-decode/source/browse/trunk/Encoder/v2/resources/ch.properties

My input (sorry for delay): Manufacturer name = constant ; modify the source code only Device Product name = constant ; modify the source code only Device Serial name = Is apparently stored on the Micro-controller's HEAP, but I haven't found a way to successfully change this on the fly (think its due to using all the available memory up) ; for now .... modify the source code only.

Maybe try altering the delays after the screen resolution string? the other keys might not be triggering within the new pop-up window. Also, 2.6 branch implements proper ISO country-codes so uk=Ukraine gb=Great Britain. Also vidpid.bin is meant to be located on the root of the sdcard; but it is not affecting you, otherwise there would be no keystrokes.

If your using macports (or alternatively brew), you need to install libusb and automake. for dfu-mode, hold the tiny black button down on the duck continuously as you insert it into the USB port.

If your Windows based, you probably want to read up on "Windows Sysprep". Handy; but sometimes it can drive you mad... Failing the Sysprep process, my second option is to use imaging software & boot cd like Acronis True Image (build 1x working image to build them all) It is how I've maintained corporate images in the past.

It works fine :)

Just reminding folks on some of the different flavours of the firmware that are already available.