no42

The latest community enchantments are available at: http:///code.google.com/p/ducky-decode

Thank you. I will do my best to keep this forum in shape. Snake

Had to patch the encoder, version 2.3 should now be available. Now you can use: ALT-SHIFT In Ducky script to trigger the Input Language Swap function in Windows.

Nope. Can you provide screen dumps of the following commands: dmesg mount [how the error is generated] Can you also use spoiler tags, to make the page more readable when you provide these logs. Thanks

OK, Initial speed test using HS2testW (http://www.heise.de/download/h2testw.html) using the default sdcard that came with the Ducky. Has put the Ducky's write/read speed at an average of 88KB/s (surprisingly slow) After liaising with Atmel Tech Support, today I have almost doubled this speed to 155KB/s, and this is as far as I have got. It means playing around with all the clocks - its quite tricky (doesn't help that all their examples are tied down to 12MHz), its a bit of trial and error to raise the Ducky's speed. Turns out everything they publish is using 12MHz even though the chip supports a maximum of 60MHz. Update: Cant get it any faster at the moment. Version 2.1 of Twin_Duck & USB_Duck have been uploaded to Ducky Decode, so you can test the latest version improvements. Recap: Wont reach SD speeds (2MB+) as its proprietary (ie licensing and membership - $2000+ per year, correct me if I'm wrong?) either way to keep costs low :) this is all open source/freeware

Information on the PoC (before Xmas) is here: http://forums.hak5.org/index.php?/topic/28162-introducing-twin-duck-firmware/?p=214115 Now you can use DuckyScript to deliver a HID payload rather than the previous hard-coded executable. You can use the following code to search for the drive via label for /f %d in ('wmic volume get driveletter^, label ^| findstr "DUCKY"') do set myd=%d then execute a binary on the ducky by %myd%/my_executable.exe or %myd%/my_batfile.bat Other Info is on the website, in my signature.

Yes - Look at Twin Duck Firmware (c_duck_v2.hex), it can be executed straight from the HID payload. There should be info in the forums, Overwraith has some demo code somewhere?

Have you tried re-formatting the sdcard as FAT32?

The version if kismet provided by Debian/Ubuntu is 2008-05-R1, which is too old to support the Ubertooth plugin. In order to use Ubertooth with Kismet it is nessecary to compile Kismet from source: sudo apt-get install libpcap0.8-dev libcap-dev pkg-config \ build-essential libnl-dev libncurses-dev libpcre3-dev \ libpcap-dev libcap-dev wget http://www.kismetwireless.net/code/kismet-2011-03-R2.tar.gz tar xf kismet-2011-03-R2.tar.gz cd kismet-2011-03-R2 ln -s ../ubertooth-2012-10-R1/host/kismet/plugin-ubertooth ./ ./configure make && make plugins sudo make suidinstall sudo make plugins-install Add "pcapbtbb" to the "logtypes=..." line in kismet.conf

It has moved to github: https://github.com/hak5darren/USB-Rubber-Ducky/wiki Edit: Some helpful resources are additionally here: http://code.google.com/p/ducky-decode/wiki/Index?tm=6 Thanks Snake

Now if I gave you all the answers.... you wouldn't necessarily learn anything. If you look at the similarities of the HID and Multi-HID source, you should be able to work it out. If you have any questions, I'm willing to answer them. If you can work out the source, I will consider bringing you into the community development team to help out! (Applies to anyone) So please forgive the staged information feed. Consider it an initiation test :) I could sure use the help!

This might help: http://www.debian-administration.org/articles/412 From what Ive noticed: <VirtualHost www.example site.com> should be <VirtualHost * > ServerName http://ip of server/ should be the name not ip e.g ServerName assisted-living-facility.com

Easy mod. With the LEDs Im assuming you mean the Ducky's - these are easy to disable, they're currently enabled to help debug problems.

The only criticism is that the Ducky doesn't always end up on E:\ Consider the following code, that searches for the drive label to get you the drive letter: for /f %d in ('wmic volume get driveletter^, label ^| findstr "DUCKY"') do set myd=%d then use %myd%, in place of e:/f:/g: whatever... Notes: You need wmic installed (XP+ for this to work)

Think the command is actually: CTRL-ALT DEL

Unless you know its output volt-age and amp-age, I would advise against it. I have heard that people who have used the wrong adapters with the raspberry pi, and have ended up blowing their device. Your risk! Not mine.

USB to AC sounds bad! USB is typically 5 volts. AC is usually around 110v(us) 220-240v(europe) Guess it depends on your adapter's current (Amp-age) and output Voltage. I'd be very careful! Excessive voltage will cause breakdown and arcing, either between separate exposed contacts (especially little points of solder), or through an insulating or dielectric barrier (for example, the dielectric in a capacitor). Excessive current is generally caused by excessive voltage. Passive components have a specific, fixed resistance; the current through them is determined by Ohm's law, I = V/R. Excess current can cause overheating and burn-through of components, leading to open circuits.

Seems to be hyped-threat of the month! I find most manufacturers (in UK/DE) now disable UPNP by default (no idea about US sorry). The issue has been around since 2009?, the issue was presented at a past-Blackhat and Defcon-16, with some tools like upnpscan Strange it suddenly jumped into a media-hype. Think it was all started by HD Moore this time around? correct me if I'm wrong.

How are you calling it? just to check?

Tricky, I dont have the facilities to practically test the speed today. But in theory: The SPI uses a 12 MHz clock (from conf_sd_mmc.conf) <- this is the limiting factor (as USB should support a maximum of 12Mbps) People from AVRfreaks claim 340 KBytes/sec for writing a 100 MB file. Hope this helps. Snake

This post may be of help. Snake

Friday is comming.......

I have karma working on the wr703n, just have to play around with the interfaces and iptables, inorder for it to work correctly. I started from a clean build. (Openwrt Attitude Adjustment). Installed karma (opkg install karma), then copied the hostapd_cli from the pineapple :) Otherwise, karma definately works, just have an interface/routing problem with iptables. UPDATE: Got it routing traffic through ICS through default Openwrt interface and iptables configuration. Karma can pick up clients. Works well, but doesnt work in Lobbying environments, as the DHCP is given by the ICS, rather than the Pineapple.

Thank you (Dnucna) for giving me the time by taking on the Encoder challenge. Hopefully, this year we can increase language support.