-
Notifications
You must be signed in to change notification settings - Fork 27
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
U2F support. #51
Comments
@alexlarsson The implementation needs to use libudev.so.1, I guess it's hardly doable ATM, right? |
Its possible to build libudev in a flatapak. Whether it works depends on how the app uses it. If you grant --device=all permission then all the devices will appear in /dev, and libudev can see them + /sys and do some stuff. However, the host side udev database which is build by udevd is not visible in the sandbox, and the upstream claims it is not abi stable so we can't expose it. I'd say, try it. |
Obviously (for isolation/sandboxing reasons, i.e. security reasons) one does not want to expose all USB devices to a browser application. So I decided to tackle this issue, where it can (I think) be solved: In flatpak. Here is a new issue: |
A permanent temporary solution would be to run |
Firefox has U2F support hidden behind a config flag. I've just tried it with Firefox 57 on Fedora 27, it worked, but it didn't work in the Flatpak Nightly version.
The text was updated successfully, but these errors were encountered: