mame82

Guys, here's a commit containing a layout addition for DA. You might find it useful, as it shows which parts of code have to be touched: https://github.com/mame82/LOGITacker/commit/f44c0c1cff622fa63c8a9763540216d22a442bba

I totally agree with @RoganDawes. Anyways, in one of my test systems I inspected weird behavior: Once the payload typing to the hidden powershell Window starts, I'm not able to...

It doesn't depend on the Unifying receiver, but on the firmware version, which kinds of vulnerability exists. Rule of thumb: Only the oldest Unifying receiver firmwares accept plain injection (MouseJack)....

Reverse mapping to raw HID keycodes (human readable) is doable and already part of the log (and only of log) output. LOGITacker currently doesn't utilize heap, and thus keeps no...

Here's an example on USB keyboard pass through to a terminal running on Android. https://twitter.com/mame82/status/1150762540080783360 Please note, the keys only arrive if the terminal has input focus (no camera picture),...

Almost all Logitech receivers have vulnerabilities, which ones depends on the firmware version. This includes for example CU0007, CU0008, CU0010, CU0012, CU0016

If you ask for pairing, this is supported for: - Unifying (cu0007, cu0008, cu0012) - G-Series Lightspeed (cu0008) - G700 (cu0007) Pair sniffing is additionally supported for: - Spotlight (cu0016)...

It depends? Could you be more clear on your use case?

If a device it out of range and no frames are received, RSSI can't be updated. In as "discover" mode is pseudo promiscuous, the probability of missing valid device frames...

Add up, just in case I get you wrong: For passive enum, it should be possible to track RSSI for the monitored device. If it is updated in the device...