> In less than 60 seconds and with the help of a rubber ducky, the thief could literally cause millions of dollars in damages to your organization. Kudos for t

> In less than 60 seconds and with the help of a rubber ducky, the thief could literally cause millions of dollars in damages to your organization. Kudos for the imagination, but in real life for most developers not vendorizing and auditing their dependencies (+ downloading them all from production) is most likely to cause such havoc (regardless if dozen thousands or millions of damage)... I imagine this might likely happen in places like security and programming language conferences, especially when you leave your belongings around unattended for a minute or two. The ideal scenario IMHO would be to have to authorize/reject devices from connecting to your machine (and limiting the scope). I don't know much about USB-C and know it is hard, but I see Apple coming up with something like this in the future (maybe along with Apple Watch detection for quick logout - you can already use it for logging in).