[Pkg-auth-maintainers] Bug#987727: Bug#987727: fido2-tools: does not find available fido2 tokens

[Taowa]

Control: severity -1 wishlist

Hi Andreas,

As far as I can tell, fido2-tools only speaks USB (and has experimental
support for NFC, but...):

> libfido2 provides library functionality and command-line tools to
> communicate with a FIDO device over USB, and to verify attestation and
> assertion signatures.
(https://developers.yubico.com/libfido2/)

Setting this bug to "wishlist" severity, and I'll look into whether this
is something upstream might want to support.

Taowa

Andreas Kemnade, 2021-04-28 11:57 -0400:
> Dear Maintainer,
> 
>    * What led up to the situation?
> I paired a FIDO2 device via bluetoothctl
> FIDO service is available and found:
> $ mdbus2 -s org.bluez /org/bluez/hci0/dev_D0_CF_5E_06_F9_C4/service002d org.freedesktop.DBus.Properties.GetAll org.bluez.GattService1
> ({'UUID': <'0000fffd-0000-1000-8000-00805f9b34fb'>, 'Device': <objectpath '/org/bluez/hci0/dev_D0_CF_5E_06_F9_C4'>, 'Primary': <true>, 'Includes': <@ao []>},)
> 
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> I tried to list the available devices via fido2-token -L and tried to get
> information about these devices via fido2-token -I
>    * What was the outcome of this action?
> $ fido2-token -L
> $ fido2-token -I D0:CF:5E:06:F9:C4
> fido2-token: fido_dev_open D0:CF:5E:06:F9:C4: FIDO_ERR_INTERNAL
> 
>    * What outcome did you expect instead?
> I expected to see the list of available FIDO2 devices and information
> about that particular device. NB: I would expect better documentation in the manpage how to properly specify a device in the commandline parameters.


-- 
Taowa (they)
people.debian.org/~taowa
LOC FN35EM