Reader access conflict with opensc-pkcs11 under p11-kit

[pboguslawski]

When p11-kit is configured to use ykcs11 + opensc-pkcs11 (opensc-pkcs11 configured to ignore readers with "YubiKey" in name) ykcs11 reports 3rd party readers that are handled by opensc-pkcs11 (in this system only 3rd party reader with 3rd party card is connected):

me@myhost:~$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/p11-kit-proxy.so --list-slots
Available slots:
Slot 0 (0x11): Alcor Micro AU9540 00 00
  (empty)
Slot 1 (0x12): Alcor Micro AU9540 00 00
  token label        : [...]
  token manufacturer : OpenSC Project
  token model        : PKCS#15
  token flags        : login required, token initialized, PIN initialized
  hardware version   : 0.0
  firmware version   : 0.0
  serial num         : [...]
  pin min/max        : [...]

me@myhost:~$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/libykcs11.so --list-slots
Available slots:
Slot 0 (0x0): Alcor Micro AU9540 00 00
  (empty)

Can ykcs11 be used in parallel with opensc-pkcs11 (ykcs11 for YubiKeys and opensc-pkcs11 for all other readers/tokens)? Any reader filtering possible in ykcs11 maybe to avoid conflict?

Related: #272

[qpernil]

For the yubico-piv-tool command line tool there is optionally simple prefix string matching, but ykcs11 doesn't have this. Part of the problem is how the filter would be specified, but I suppose an environment variable would do..