Hi, no we were not able to test all the different U2F devices before merging them since we do not own most of them. However, the way I see it, and feel free to disagree, is that adding an entry in that udev rule (or an equivalent one) is a required step for any device to work. The library itself may still be incompatible with a specific device for different reasons, but I don't think that incorporating a bigger list poses an issue.
That being said, if it helps we can make a new release of libu2f-host. A. On 2 June 2017 at 22:50, Nicolas Braud-Santoni <nico...@braud-santoni.eu> wrote: > X-Debbugs-CC: ales...@yubico.com, k...@yubico.com > > On Fri, Jun 02, 2017 at 05:10:52PM +0200, Michael Biebl wrote: > > Am 02.06.2017 um 16:14 schrieb Andreas Gnau: > > > Hello, > > > that patch seems to be a bit old. The latest GIT-version has quite a > few > > > more HW-IDs and I think it would be very beneficial to have the latest > > > version in stretch in order to provide out-of-the-box support for as > > > many tokens as possible. > > > > > > https://github.com/Yubico/libu2f-host/blob/ > e6ee395fc7ee66884adefb2056a40a8e4ca514fd/70-u2f.rules > > > > Nicolas, your call. Feel free to send me an updated patch or let me know > > if I should use the one you sent earlier. > > I would not be super-comfortable shipping the ruleset from libu2f-host's > development version in stretch, given that I cannot test it with any of the > new devices. > > Were this a released version, I would feel much more confident about it, > if only because it would be exposed to users. > > @Alessio, Klas: Were you able to test those rules before merging upstream? > Do you have a new release planned soon? > -- Alessio Di Mauro Software Engineer | Yubico <http://www.yubico.com/>
