On Sun 17 May 2026 at 09:49:13 (+0200), [email protected] wrote: > USB devices identify themselves with a couple of numbers: the device > class, the vendor ID and the product ID [1],as defined by the vendor. > > The device can do whatever it wants, it's just firmware pushing bits, > so no -- it can tell your computer whatever it wants. > > The operating system then uses these IDs to decide what to do (e.g. > load a kernel driver, whatnot). Udev is the one responsible for > that in our countries.
I agree. The more that udev can inform us about, the better. My own udev scripts are a tiny part of that. Obviously you have to be careful with keyboards, as you need a device for submitting your response! > But Stefan's approach went another way: ask the user (they are, after > all, those sticking the thing into the port). If you stick your device > to a charger and it asks you "is connecting to this keyboard OK?", > it's on you to say "HELL, NO!" :-) > > Having that as an option makes sense. Sure. But I thought charging ports were done and dusted about five posts upthread (power-only cable/power bank/mains adapter). The approach is akin to assuming all fuel pumps have had a credit-card skimmer installed (but more practical). Cheers, David.
