I'm thinking about setting up a #udev rule that triggers some actions when a given device is removed. For that I'd like a minimal #usb device/token, think "only vendorid and productid", no actual functionality (which could fail and cause issues, etc.). Does anyone have a source for something like that? It's obviously ridiculously niche and not at all cost-effective to manufacture...
@lpwaterhouse you can do this with any USB device you can imagine. Do it with a flash drive. Doesn’t matter if the flash is corrupt or dead, you’ll never access the flash anyway.
@feld I know that can :-D The question is about making sure nothing automagic can try to load or even access any kernel module, e.g. it should not identify as a HID or storage, etc. For that it should ideally have a VID/PID combo that is reserved for that use (Essentially a Null-Implementation). I'm just curious whether someone actually makes such a thing, e.g. as a dongle, or has figured out a microcontroller with the absolute minimum of intelligence for it and published that finding.
@lpwaterhouse I don't know how do you avoid it though? Unless you chop up a USB HUB and use that? It needs to be some fully compliant USB thing which means a device or a hub, right?
@feld Exactly why I'm asking. As far as I understand the spec (not my field of expertise) it should be sufficient to perform the initial handshake (e.g. provide VID/PID and device class) and then do nothing else. That should not even require a full-blown microcontroller, but could be done with an ASIC or even discretely. Unless it's for my exact use-case manufacturing that is obviously not economical; with microcontrollers costing mere cents. But there's always the chance that someone had the same thing tickle their brain-case before and they've made it available (for example with incredibly niche things like https://onerng.info/)
Add comment