usb-ks

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 22562bf35fcb7d8acf32ca4ac35b929628763143
parent fb9c11f231e5f1a1116c6148b6320df0c7715436
Author: Andrew Laack <andrew@laack.co>
Date:   Sun, 15 Mar 2026 16:32:22 -0500

Messaging

Diffstat:
MREADME.md | 6++++--
1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md @@ -1,6 +1,6 @@ # usb-ks -usb-ks is a USB killswitch program, inspired by [https://github.com/BusKill/buskill-app](https://github.com/BusKill/buskill-app), but simplified and written in Go instead of Python. Additionally, usb-ks executes the specified command on all USB device changes, not just disconnects. +usb-ks is a USB killswitch program, inspired by [https://github.com/BusKill/buskill-app](https://github.com/BusKill/buskill-app), but simplified and written in Go instead of Python. Additionally, usb-ks executes the specified command on all USB device changes, not just disconnects. When governments seize devices they often use USB devices to exfiltrate data and to ensure systems with FDE don't shutdown. It is thusly evident shutdown behaviors should be initiated on connection and disconnection. # installation @@ -27,7 +27,9 @@ Basic invocation, executing xscreensaver on USB device change: ```usb-ks``` -Execute `shutdown` on USB device change: +NOTE: Since xscreensaver does not shutdown your system (i.e. doesn't engage FDE protections), it may not be desirable for certain threat models. + +For proper production usage I would recommend using `shutdown`: ```usb-ks shutdown```