Jump to content

no42

Dedicated Members
  • Posts

    925
  • Joined

  • Last visited

  • Days Won

    17

Posts posted by no42

  1. 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 ;) )

  2. 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.

  3. 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.

  4. 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.

×
×
  • Create New...