[Question] Is there now a working German Encoder?

[AustriHacker]

Hey, just got my USB Rubber Ducky, and now i cant find a working Ducky Encoder for German. Can anyone help?

[no42]

Theres kinda 2x on http://code.google.com/p/ducky-decode/

Your better off, downloading the svn.

Version 1 PoC, needs to be compiled.

Version 2.1 is a lot better

java -jar duckencoder.jar -l resources/de.properties -i infile.txt -o inject.bin

if you can report any problems, I will help you resolve them.

[AustriHacker]

Well I used the Version 2.1 and this is the result:

$ java -jar encoder.jar -i script.txt -o inject.bin -l de.properties
Char not found:UNICODE_201A
Char not found:ISO_8859_1_FB
Char not found:UNICODE_221A
Char not found:ISO_8859_1_BA
Char not found:UNICODE_201A
Char not found:ISO_8859_1_FA
Char not found:UNICODE_221A
Char not found:UNICODE_221A
Char not found:ISO_8859_1_BA
Char not found:UNICODE_221A
Char not found:UNICODE_221A
Char not found:UNICODE_201A
Char not found:ISO_8859_1_FA
Char not found:UNICODE_201A
Char not found:ISO_8859_1_F9
Char not found:UNICODE_221A
Char not found:ISO_8859_1_BA
Char not found:UNICODE_221A
Char not found:ISO_8859_1_BA[/CODE]

Could you please help me? I guess i will have to patch the de.properties, if u tell me how, ill do it and hand u the patch if u wish.

[no42]

Look up your charset here: http://www.charset.o...ractersets.php?

Then you have to match up the character to a sequence of key-scan codes (40,45,100) or their US QWERTY equivalent (HID_A, HID_B MODIFIER_SHIFT etc)

insert the additional lines into resources/de.properties

i think the following examples are right? I could be wrong:

ISO_8859_1_FB = HEY_LEFT_BRACE
ISO_8859_1_BA = HID_TILDE, MODIFIER_SHIFT[/CODE]

continue, the process for the rest of your characters. Publish the patch on the "issues" section of ducky-decode, and ill push the changes into the svn.

Thanks for your support.

~Snake

Edited December 23, 2012 by midnitesnake

[no42]

ISO_8859_1_A0 = KEY_SPACE // 160 Nonbreakng Space											
ISO_8859_1_A4 = KEY_E, MODIFIERKEY_RIGHT_ALT // 164 ¤ Currency Sign	
ISO_8859_1_A7 = KEY_3, MODIFIERKEY_SHIFT // 167 § SECTION SIGN											
ISO_8859_1_B0 = KEY_TILDE, MODIFIERKEY_SHIFT // 176 ° DEGREE SIGN											
ISO_8859_1_B2 = KEY_2, MODIFIERKEY_RIGHT_ALT // 178 ² SUPERSCRIPT TWO											
ISO_8859_1_B3 = KEY_3, MODIFIERKEY_RIGHT_ALT // 179 ³ SUPERSCRIPT THREE
...
I've abbreviated the list - as theres a lot of missing codes at the bottom

These are already in de.properties - looks like theres no translation for circumflex_bits & acute_accent_bits and grave_accent bits, it might be easier to change these labels to a particular key e.g. MODIFIERKEY_RIGHT_ALT

Edited December 23, 2012 by midnitesnake

[AustriHacker]

Hey, well after some trying i found out it was not the de.properties that made those problems, it was my Script. I copied some Text from a Word into a Text Editor and then tried to encode it. After retyping the ext same text manually i found out there is in fact only one Char missing: UNICODE_221A -> and it is only missing when trying to encode " ä " or " ß " But why is the same Char missing when trying it with 2 different Characters ?

I hope this could help anyone resolve this problem.

[no42]

how are these characters normally accessed? are they accessed through another keypresses and shift?

I think there may be two different keyboard types T1 and T2? might still work by editing the de.properties file?

Ive got Unicode-221A as the following (needs 3-bytes, whereas the ducky only currently supports 2-byte codes, but i dont see how this is causing the problem with those 2x chars)

U+221A √ e2 88 9a SQUARE ROOT

Edited December 24, 2012 by midnitesnake