3 ms·
Seems wireless keyboard vulnerabilities can also be problems accidentally... Just a couple years ago, I was finalizing and testing some factory stations we'd b
by neilv 4y ago
Seems wireless keyboard vulnerabilities can also be problems accidentally...
Just a couple years ago, I was finalizing and testing some factory stations we'd built (incorporating industrial NUCs) before they'd be flown to Asia for installation in a production line.
Someone had ordered a name-brand wireless keyboard with USB dongle, and I'd said we probably don't want wireless keyboards nor their dongles in the factory, but I figured it was OK to use briefly for testing, since it's what we had handy.
Was getting phantom key events, which initially was alarming, because I'd had to get creative with some device drivers and the Linux input system. But then it also happened during BIOS/UEFI setup.
There was one other person in the shared tech/lab space at this time, so I go over and ask if they happen to be doing anything with RF... It turns out they were also using the same brand of wireless keyboard, which seemed to intermittently be barging-in or interfering with mine, in such a way to generate valid USB input device events.
When I brought it up with colleagues, we were all baffled, since presumably the name-brand would like to sell fleets of wireless keyboards to entire open-plan office building floors at a time, and would design it to work well for that use case. But it did indeed seem that activity on one keyboard was triggering events out the USB dongle on another.
(I won't mention the brand, since I didn't investigate rigorously, and write it up. We were crazy-busy, launching our startup's MVP. Fortunately, without the wireless keyboards, the stations were rock-solid for the entire year-plus deployment, against all odds.)