Skip to content
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

[TASK] Enable USB for Extensions in Chrome #4205

Closed
ghost opened this issue May 6, 2018 · 1 comment
Closed

[TASK] Enable USB for Extensions in Chrome #4205

ghost opened this issue May 6, 2018 · 1 comment

Comments

@ghost
Copy link

ghost commented May 6, 2018

re #4060 (was #717)


Important

#5050 has implemented ledger-support and thus closed #4060 via #4593. Superseded legacy-issue #717 was closed, too.

Despite the above, this issue here (USB for Extensions) should stay open and WebUSB implementations should be tracked (and even pushed, e.g. via super-bounties on more general bounty-systems, like e.g. https://www.bountysource.com.


via WebUSB

From #4060 (comment))

It looks like the Chromium devs would be more open to making WebUSB available to extensions than U2F

From https://bugs.chromium.org/p/chromium/issues/detail?id=770896

We're very interested to see this happen as it would enable us to use WebUSB for the Hangouts Meet speakermic to use together with a Hotrod / CfM running in kiosk mode.

via U2F

Unverified/unconfirmed statement from Chrome project:

This is working as intended. There is currently no clean way of determining an appropriate origin of an extension for the purposes of populating clientData in the U2F protocol. Thus U2F support is limited to web pages.

https://bugs.chromium.org/p/chromium/issues/detail?id=823736#c4

Requirements

A patch for the Chrome Browser is created, which fulfills the requirements of the Chrome Team.

The patch must be accepted and applied to the public Chrome Browser.

@ghost ghost changed the title [TASK] Enable U2F for Extensions in Chrome [TASK] Enable USB for Extensions in Chrome Jul 2, 2018
@ghost
Copy link
Author

ghost commented Dec 3, 2018

@bdresser , me closing this, to get it off my issue-list.

Anyone interested in this issue should follow the 2 mentioned chromium issues.

@ghost ghost closed this as completed Dec 3, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants