On 2018-02-18 13:49, Bastian Blank wrote:
On Sun, Feb 18, 2018 at 10:08:39AM +0900, Hideki Yamane wrote:On Sat, 17 Feb 2018 19:32:09 +0100 Bastian Blank <waldi@debian.org> wrote: > And chromium does not recommends that at all. Really? What's wrong with it, I'm curious.Well, if you need something, in this case some udev rules to actually be able to access the hardware, then you should recommend it. And as chromium does not pull in the library, then somehow it needs to get the udev rules.
FWIW a future version of the proprietary google-chrome-* will pick up libu2f-udev as a recommends as well - probably with M66 somewhen in late April, early May. It now landed on Chromium master. If you think it needs to be pushed more quickly, please let me know in private.
That said, I think Paul's suggestion on just installing the right packages when a u2f device is found makes sense as well. But they might be somewhat transiently connected and I don't think there are prompts on device plug-in?
Kind regards and thanks Philipp Kern