[pkg-gnupg-maint] yubikey udev rules: ATTRS{} vs ATTR{}, lintian, and AppStream providers

[Daniel Kahn Gillmor]

On Fri 2018-08-24 17:48:29 +0900, NIIBE Yutaka wrote:
> Daniel Kahn Gillmor <dkg at fifthhorseman.net> wrote:
>> Question 1 (for gniibe)
>> -----------------------
>>
>>     Can you confirm whether udev needs to search "up the devpath" to
>>     identify the Yubikey devices?
>
> No, it's not needed to search up.  ATTR is OK for our use case of
> scdaemon.  We can assume that Yubikey supports CCID interface.

thanks!  I've updated both the udev rules and the AppStream metadata.

> Please note that a single Yubikey device supports multiple interfaces.
>
> My guess is that the entries are originally written with its interface
> (ATTR{bInterfaceClass}==11 to distinguish CCID device).  That is, the
> original entries are specifically for device with CCID interface.
>
> We don't need that.

I don't see anything matching bInterfaceClass in udev rules or AppStream
(indeed, the only thing even mentioning bInterfaceClass in the source is
scd/ccid-driver.cc).  If you're suggesting any specific changes to the
debian packaging, i'd be happy to merge them, please propose them more
concretely :)

Regards,

        --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20180824/d93ab102/attachment.sig>