-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the use case? #137
Comments
One such example that comes to mind (as a user and contributor of the following project) is https://www.numworks.com/blog/webusb-firmware-update/ |
One use-case for security-minded folks is getting whole new attack vectors. If you make a living writing exploits this could come in handy! |
My opinion is that WebUSB is very useful if you are a vendor of a hardware that wants to allow to be accessible from the web. The API is nice. And browsers are now a de-facto operating systems whether you like it or not. However, I agree that the current model of WebUSB "any device can talk to any website" is dangerous - and originally, WebUSB was not open like that! - and hardware vendor had to specifically whitelist domain URLs. This would be a much better compromise between security and usability. Whitelisting was removed here as a move away to feature policy (similar to how webcams etc are handled) - #86 - I think both feature policy AND the explicit URL whitelisting would be good. (At that time I also thought this would be a good idea though.) See my issue #127 that I still stand behind :) |
I think this thread has done a good job of documenting a number of use cases for this API. Thanks all! |
With the ubiquity of USB based attacks I wonder, what is the use case for allowing typically insecure user program (web browser) to connect to USB?
What problem is this solving?
The text was updated successfully, but these errors were encountered: