|
|
|
|
|
by Animats
4107 days ago
|
|
Right. A USB device can't do anything unless the OS lets it. We went through this with "autorun" on CDs and DVDs. For years, Windows would run anything that looked executable if you put it in the obvious place. That didn't end well. Those defaults were finally changed. What's needed is to turn off automatic hot plugging for USB devices. The era when you can plug in a USB device and have it go live without user interaction is over. We're going to need clear OS dialogs - "The USB device you just plugged in claims to be a keyboard - did you just plug in a keyboard?" You should't be able to boot from a USB device without doing something to enter a maintenance mode. There's nothing special about USB Type C here. It's just that the asymmetry of USB is being dealt with. Asymmetrical USB has created an amusing hierarchy. Desktop computers were masters. Phones were slaves. Then came tablets. Are they masters or slaves? |
|
The problem with that is that you inevitably run into this dialog with nothing else attached to the machine. How are you going to confirm the dialog?
Better to focus on isolating the keyboard driver from the rest of the OS, so the only thing it should be able to do is read in input from the keyboard and report it back to the OS.