[Pkg-auth-maintainers] Bug#888892: No permission on U2F security key

[Kurt Roeckx]

On Wed, Jan 31, 2018 at 02:08:14AM +0100, Michael Biebl wrote:
> Control: reassign -1 libu2f-udev
> 
> Am 31.01.2018 um 00:38 schrieb Kurt Roeckx:
> > On Wed, Jan 31, 2018 at 12:06:48AM +0100, Michael Biebl wrote:
> >> Am 30.01.2018 um 23:47 schrieb Kurt Roeckx:
> >>
> >>> There is no such package, but I do have u2f-host instaled, and so
> >>> libu2f-host0 and libhidapi-hidraw0. I also have libykpers-1-1
> >>> installed that ships /lib/udev/rules.d/69-yubikey.rules
> >>
> >> Seems the package was named libu2f-udev, not libu2f-common.
> >> You want /lib/udev/rules.d/70-u2f.rules most likely.
> > 
> > That seems as good as the same as
> > /lib/udev/rules.d/70-debian-uaccess.rules, which actually seems to
> > cover more devices. So it was not installed, installing it didn't
> > have any effect.
> 
> You should report your device to libu2f-udev then. Reassigning accordingly.

Maybe I wasn't clear. My devices are in both files, but even when
it's in those files it does not work. reassigning it to
libu2f-udev is not going to fix my problem.

But the files in libu2f-udev do seem to be outdated compared to
the one in udev, so maybe you should have cloned this?

> As announced, /lib/udev/rules.d/70-debian-uaccess.rules will go away.

I really think that something that is installed by default should
make sure it's set up correctly. I also think a list with U2F
devices is the wrong way. This would be like for every USB memory
stick, mouse, keyboard and so on you would need to say what type
of device it is, what driver to use before you can use it.
Something should really detect that it's a U2F device in some other
way than by checking some IDs.


Kurt