Running directly in the browser is also not how I'd want to do USB.
replyWhen the alternative is downloading arbitrary executables I find the browser sandbox to be a reassurance.
replyExcept the sandbox is a huge target already, and breaking it means any website can now access and mess with your usb devices. If you can develop an exploit for Chrome's WebUSB system, you potentially have millions upon millions of targets available.
replyDownloading an arbitrary executable can be made safe (via multiple avenues: trust, anti virus software, audits, artifact signing, reproducible builds, etc) and once the software is vetted, it exposes (or it should at least) little to no attack vector during daily use.
> trust, anti virus software, audits, artifact signing, reproducible builds, etc
replyMy mom has six weather apps on her phone.
Buddy if your "sandbox" lets code inside it replace your keyboard's firmware you don't have a sandbox.
replyProgramming your keyboard is actually a common case! See usevia.app
replyIt is indeed common!
replyBut a keyboard flashed with malicious firmware becomes an undetectable keylogger, a USB rubber ducky, and a virus-laden USB stick all in one.
The concept that someone would want to reflash their keyboard firmware, but wants a sandbox because they don't trust the firmware programmer makes no sense.
Then don't install the extension
replyIt is enabled without extension in Chrome browsers. This is a common complain about Firefox is that they don't implement the Google draft spec.
replyIt will probably come natively one day in Firefox, and we should push back against such attack vectors.