You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 9, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2023. It is now read-only.
Cannot call u2f.register from another extension #158
Digging further, this appears to be an error in sendResponseToActiveTabOnly @ u2fbackground.js
The function tries to determine if the tab that made the registration request is still active. To do so it accesses sender.tab.id, where sender is a MessageSender. However, I am calling from an extension, not a tab, and thus sender.tab is undefined.
This code path seems to only be for Register responses.
I don't see a good workaround for this. Unfortunately, I cannot absorb the u2f-chrome-extension into mine, because the u2f-chrome-extension requires some black magic to get permissions to the usb. I also can't seem to communicate directly with the built-in chrome from my extension.
There are actually multiple issues with calling u2f-ref-code from another extension. There are a lot of assumptions throughout the code that the origin is http:// or https://, not chrome-extension://.
Enabling this will probably be a lot of work (more than I can probably do).
Activity
steamraven commentedon May 12, 2017
There are actually multiple issues with calling u2f-ref-code from another extension. There are a lot of assumptions throughout the code that the origin is
http://orhttps://, notchrome-extension://.Enabling this will probably be a lot of work (more than I can probably do).
Some areas I already found, more probably lurking
tayler-king commentedon Dec 4, 2018
Has anybody found any way around this? Seems like Chrome actually blocks other extensions from accessing the U2F extension (
ERR_BLOCKED_BY_CLIENT).