So it appears that to load a PKCS11 module in snap packaged FireFox requires:
1) "/run/user/[0-9]*/** mr,"
2) "/run/pcscd/pcscd.comm rw," (if module uses pcscd)
3) absolute path (i.e. no symlinks) to the module
4) all libs the module may need to be in the snap base
So how should a snap package handle arbitrary pkcs11 packages that require libs that would have been installed in a traditional install, but are not by snap packaging?
So it appears that to load a PKCS11 module in snap packaged FireFox requires: [0-9]*/ ** mr," pcscd.comm rw," (if module uses pcscd)
1) "/run/user/
2) "/run/pcscd/
3) absolute path (i.e. no symlinks) to the module
4) all libs the module may need to be in the snap base
To test if (4) is correct:
https:/ /launchpad. net/~ascaneo can you run "ldd /usr/lib/ libeToken. so.10.7. 77"
https:/ /launchpad. net/~liuck can you run "ldd /usr/lib/ bit4id/ libbit4xpki. so"
I posted the output of "ldd opensc-pkcs11.so" in https:/ /bugs.launchpad .net/ubuntu/ +source/ firefox/ +bug/1967632/ comments/ 18
It requires "libopensc.so.8 => /lib/x86_ 64-linux- gnu/libopensc. so.8" which is most likely not in the snap package base as per https:/ /bugs.launchpad .net/ubuntu/ +source/ firefox/ +bug/1967632/ comments/ 17
So how should a snap package handle arbitrary pkcs11 packages that require libs that would have been installed in a traditional install, but are not by snap packaging?