search

Nitratz / ducky-decode

Automatically exported from code.google.com/p/ducky-decode
0 stars 0 forks source link

Simulation of MUTE Key is not possible #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Try to build a payload sending KEY_MUTE erevry 2 seconds, like
DELAY 2000
MEDIA_MUTE
DELAY 2000
MEDIA_MUTE
DELAY 2000
MEDIA_MUTE
DELAY 2000
2. encode it and copy inject.bin to rubber duck usb
3. plugin rubber duck usb (firmware duck_v2.1.hex)

What is the expected output? What do you see instead?
I would expect (e.g. under Windows 7) that the speaker icon in the taskbar 
toggle between muted and not muted.

But nothing happens.

What version of the product are you using? On what operating system?
firmware duck_v2.1.hex
encoder V2.6.3
Windows 7 64Bit

Please provide any additional information below.

I sniffed the USB and compared it with an USB keyboard.
If I press the mute buttom on the USB keyboard I get as raw data
"02 04"
If I sniff the rubber duck usb it get
"00 00 04 00 00 00 00 00"
which is in fact a "A" and not mute

As USB scan code mute if defined as "7F". So if you change the value in the 
keyboard.properties to "7F" than of course you will get
"00 00 7F 00 00 00 00 00"
But not the MUTE key.

It is the same to other MEDIA keys !

Original issue reported on code.google.com by FossiS...@googlemail.com on 23 Jan 2014 at 4:25

GoogleCodeExporter commented 9 years ago 
Initial research has provided a second Endpoint where these keys are send over 
a second USB channel.  We still need to figure out how to create this second 
Endpoint with the right Descriptor details in the Firmware.

The Firmware and probably the Encoder will need to be rewritten.

It is on the todo list.

Original comment by midnites...@gmail.com on 25 Jan 2014 at 9:57