Re:No one, not even the Secret Service, should randomly plug...
by hopler on Monday April 08, 2019 @10:34PM
(#19611242)
You only need to authenticate a device once, when you first acquire it, or after it is tainted due to loss of physical control. This is how Bluetooth works today.
Re:No one, not even the Secret Service, should randomly plug...
by jolmg on Monday April 08, 2019 @11:32PM
(#19611537)
Maybe I'm wrong, but there's currently no sort of authentication protocol for devices in USB, right? I (and I think jimrandomh too) was thinking of USB as-is. Something that OSes can do right now without having to wait for whoever controls the USB spec. As it is, how can an OS know that the mouse it sees on waking up is the same mouse that was connected before it slept or powered off? I don't think there's any sort of cryptographic authentication specified for USB devices.
Still, requiring one to type a password in a newly connected keyboard is a pretty good idea as long as it's a configuration option. I imagine you'd also like something similar for the mouse. Maybe having to type a password on a virtual keyboard. It's annoying to have to do something like that every time a computer is woken up. You're talking about typing a password 3 times. Once to log the keyboard in, then to log the mouse in, then to select a user and log the user in.
Your other suggestions are vague, so I'm not sure what you mean by "basic". I mean, if one knows a driver is buggy, those bugs would be taken care of (from the developer's point of view; the administrator might not update the software, but what can the developer do?).
And what does it mean to "harden" a filesystem driver when a device identifies itself as a storage device? A filesystem driver should be "hard", period. All the time. That's something done when the driver is being written, not until it identifies a device.