Conversation

Notices

1. Embed this notice
   Lawrence Pritchard Waterhouse (lpwaterhouse@ioc.exchange)'s status on Monday, 22-Apr-2024 02:14:18 JST Lawrence Pritchard Waterhouse

   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...

   • Embed this notice
     Lawrence Pritchard Waterhouse (lpwaterhouse@ioc.exchange)'s status on Monday, 22-Apr-2024 02:14:16 JST Lawrence Pritchard Waterhouse

     in reply to

     • feld

     @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.

     Doughnut Lollipop 【記録係】:blobfoxgooglymlem: repeated this.
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Monday, 22-Apr-2024 02:14:16 JST feld

     in reply to
     @lpwaterhouse pretty sure you want this
     
     https://tech.michaelaltfield.net/2020/01/02/buskill-laptop-kill-cord-dead-man-switch/
     Doughnut Lollipop 【記録係】:blobfoxgooglymlem: likes this.
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Monday, 22-Apr-2024 02:14:17 JST feld

     in reply to
     @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.