no42
-
Posts
925 -
Joined
-
Last visited
-
Days Won
17
Posts posted by no42
-
-
Try :
ASCII_5E = KEY_RIGHT_BRACE, MODIFIERKEY_SHIFT
If it works I'll patch the SVN, and update the download tomorrow.
-
For those who looked for ^ in norwegian, edit the no.properties line 129:
ASCII_5E = KEY_RIGHT_BRACE, MODIFIERKEY_SHIFT
Thanks - committed to SVN.
-
what keys do you normally press for ^ ?
-
1. Seems that the default CRDA is limited to the US configuration ; UPDATE: I have successfully used iw reg set XX to change the settings for wlan1 :) but not wlan0 :(
2. Though they were 5dB, unless someone can correct me from the Design-Build-Production Team.
3. Appears stable to me on the two internal antennas at 5v, but I admit I haven't tried powering a 3rd USB alpha.
4. Is answered above.
5. Nowadays, AP's seem to auto-select a channel (default iwconfig configuration), but this can be manual set (iwconfig <interface> channel <x>)
-
Yep, brings back fond memories of April 2008 ;)
-
Firmware
In the ducky guide (there is a link in my signature) refer to appendix "Flashing Guide: Linux/OSX"
Dfu-programmer is also available through macports, but it is a pretty good walkthrough of compiling from source. To compile from source you need to download X-code from the app store, and follow the install macports walkthrough.
You can then change the firmware (if you want) to the ones found on the ducky-decode website (again see my sig for the link).
Payloads
You need Java (version 1.7, Apple only supports 1.6 so you have to get v1.7 from Sun/Java website)
Also read up on https://code.google.com/p/ducky-decode/wiki/Encoder_Howto
Once Java is installed, the application to convert your plain-text ducky script into a binary (inject.bin) the Ducky reads, is through a command line interface.
Open up a Terminal (Command-Space, type Terminal, Enter), navigate to the directory where encoder.jar or Encoder.jar is located using standard linux command-line statements.
Execute the encoder with the following command:
java -jar ./encoder.jar -i my_script.txt -o inject.bin
copy the inject.bin to the ducky's sd-card, then insert sd-card into the ducky, ducky into the computer, and hopefully your payload should trigger :)
Any problems hit up the Ducky forum/IRC where there should be at least one other person to help at any given time.
-
Are you asking how to SSH into all three using the same private key?
-
Added "COMMAND-OPTION" keyword into the SVN https://code.google.com/p/ducky-decode/source/browse/trunk/Encoder/v2/src/Encoder.java if you would like to test it?
So hopefully COMMAND-OPTION <X> will work???
If it works I'll make it mainstream.
-
Here you go,from a cmd.exe/command-prompt:
diskpart list disk <------ look for your USB select disk X <-------determine X from the 'list disk' command above clean create partition primary select partition 1 format fs=fat32 <----- or use fs=ntfs active exit
-
What key presses do you make to get the ^ char?
Edit:
Looking at https://code.google.com/p/ducky-decode/source/browse/trunk/Encoder/v2/resources/fr.properties = KEY_MINUS, MODIFIERKEY_RIGHT_ALT
are you using the language flag? " -l fr "???
Example:
java -jar encoder.jar -l fr -i input.txt -o inject.bin
-
It could be a bad/damaged sd-card?
Read the FAQ, and the Ducky Draft Guide, see if you can swap the sdcard maybe the Ducky will spring into life?
-
GPG/GnuPG/GPG4Win
They are all free... And use Public-Private Key, Ideally your friend will also use the same method?
There are a few web-isodes on the subject, can't remember the numbers, but believe it was season before last?
-
If you use a "bus-pirate" you have to enable the pull up resistors (2K – 10K ohms) - maybe this is what your missing?
-
Have you tried using the Duck encoder manually?
Example
java -jar encoder.jar -l uk -i test.txt -o inject.bin
-
Windows will do that, what happens if you plug it into linux (Ubuntu/Kali)?
Sometimes the little rubber button gets stuck, and you device is in DFU mode.
What do you see in device manager?
-
What are you trying to do? payload etc?
What commands are you using?
Have you read/watched the tutorials on usbrubberducky.com?
Have you read the FAQ? or the Ducky Draft Guide?
-
Glad you got it working :)
-
Sounds like you have a newer Mac.
The straight brute-force attack only works on older models. Though apparently you can trick the counter? apparantly by changing the keyboard language every X attempts?
There is also the following instructions to reset the firmware password on newer Macs:
- Boot with Option key held to display the boot menu’s firmware password prompt.
- Press Control-Option-Command-Shift-S to reveal a 33-digit hash (mixed letters and numbers) that contains an identifier for your specific motherboard and the Atmel chip used for your system. In this hash, the first 17 digits are an identifier for the system’s motherboard, and the last 16 digits are a hash for the password.
- Submit the hash to Apple, where someone will put it through a special utility to create a keyfile that is specific for your machine.
- Place the file on a special USB boot drive and hold Option to load the boot menu and select this drive.
The system will read the file and properly reset the firmware password stored in the Atmel chip.
-
My Bad!
These were all patched in the SVN version February 2013 thanks to Webdirector.
Looks like I forgot to apply the changes to the physical download.
UPDATE: I've now fixed the download (v2.6.1)
Thanks.
-
Individual paste bin's of the modified and new file:
functions.php http://pastebin.com/AQfwCDt4
large_tile.php http://pastebin.com/ESTMyC8X
includes/content/time.php http://pastebin.com/Tuw2nGcd
but should be simple as:
opkg update opkg install patch --dest usb [manually copy n paste patch to file, e.g. vi time.patch] patch < time.patch
-
You also need this version of firmware duck_v2.1.hex
-
did you use the "patch" command or manual add the additional code?
Could be that copying the code onto the forum has messed up the alignment/formatting, I'll stick a copy on pastebin http://pastebin.com/R1ZBaPwK
-
yep - looks like your "black rubber part" of the button has fallen out during postage?
Happened to me once. I was lucky enough to find it, and squeeze it back into its home.
I suggest going through the Hak shop for an exchange, as it sounds like your Ducky has become damaged in the mail.
Secondly,
The ducky should flash red if the card or inject.bin is not found. If it flashes green, I think its working ok. But with default (stock) firmware has limited OS support - which could be why your seeing nothing.
Without the button, its a pain to start the Ducky in DFU mode, which is needed to update the firmware to the latest community releases.
-
Ive highlighted the button in this pic: http://postimg.org/image/yrr2y582r/1678034c/
[SOLVED] ^ with a swedish keymap and DuckEncoder 2.6.1
in Classic USB Rubber Ducky
Posted · Edited by midnitesnake
think that command is using the builtin language map (unless you have unzipped and re-packaged?),