You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use OpenSC with my Yubikey PIV, the distribution package of OpenSC installs a .module file which ensures that opensc-pkcs11.so is loaded into any well-behaved applications automatically.
So I can use the PKCS#11 URI 'pkcs11:manufacturer=piv_II;id=%01' with any application in place of a filename for a cert/key, and expect it to work.
That does require that the PKCS#11 module be installed correctly with a p11-kit .module file though...
The text was updated successfully, but these errors were encountered:
dwmw2
changed the title
ykcs doesn't install p11-kit module file
ykcs11 doesn't install p11-kit module file
Oct 1, 2016
I'm not very familiar with p11-kit, if you have such a module config file I'd appreciate the contribution. Do you see anything aside of the config file that would be needed ? One thing that pops to mind is the different shared library suffixes on Linux an MacOS.
It is also possible to symlink /usr/lib/x86_64-linux-gnu/pkcs11/libykcs11.so to ../libykcs11.so.
In that case the module path provided can be a relative one - simply libykcs11.so.
When I use OpenSC with my Yubikey PIV, the distribution package of OpenSC installs a
.module
file which ensures thatopensc-pkcs11.so
is loaded into any well-behaved applications automatically.So I can use the PKCS#11 URI '
pkcs11:manufacturer=piv_II;id=%01
' with any application in place of a filename for a cert/key, and expect it to work.That does require that the PKCS#11 module be installed correctly with a p11-kit .module file though...
The text was updated successfully, but these errors were encountered: