Jump to content

f33r

Active Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by f33r

  1. f33r,

    Sorry to hear that you are having issues... With the vm are you using Virtualbox/VMPlayer/Workstation?? Reason I ask is because the Ducky (in my personal experience) does not work with Virtualbox. Have you been able to replicate this issue with any of the other payloads?

    Also i would recommend moving your firmware version to duck_v2.1.hex (http://code.google.com/p/ducky-decode/). There's a great walkthrough in the Wiki that Midnitesnake put together on flashing the duck.

    ~skysploit

    Hi skysploit,

    thks for the reply i'm using vmware workstation 9.0.

    I have tested reverse windows 7 and 8 with and without uac and all do the same... this also happens if using the ducky-encoder.

    I will test with the firmware you advice and get back with news.

  2. Hi,

    Just to start great kudos to the developer! great job.

    my prob, i just received the ducky and tested with a hello payload all works fine. but when using simple-ducky-payload-generator or just the ducky encoder to create a reverse shell with or without uac admin, in the payload.txt file all is ok but when plug the ducky to a vm with windows 7 when the tipping starts on the cmd some chars just get heated! :S

    this is result from cmd

    http://pastebin.com/0shy7hmt

    at first i thougth it had to be with the keyboard that i selected PT, but i created a hello payload with some native PT chars all ok.

    i have my ducky as stock so no firmware only testing payloads for now.

    any idea?

    thks

    f33r

×
×
  • Create New...