The proposed approach to solve this that was discussed with the Ubuntu security team is:
- stage common PKCS modules in the snap
- add a layout for `/usr/lib/pkcs11` pointing to a writeable area of the snap (e.g. `$SNAP_USER_DATA/.local/lib`)
- on first run, copy the common PKCS modules to that writeable area
- document that custom modules (and their dependencies?) should be manually copied to that directory
- create a new interface (not auto-connected, that's okay) for access to `/var/run/pcscd/pcscd.comm`
I'm not familiar with how smart card readers work though, so feedback and suggestions are welcome.
(from https:/ /bugs.launchpad .net/ubuntu/ +source/ chromium- browser/ +bug/1843392/ comments/ 1)
The proposed approach to solve this that was discussed with the Ubuntu security team is: USER_DATA/ .local/ lib`) pcscd/pcscd. comm`
- stage common PKCS modules in the snap
- add a layout for `/usr/lib/pkcs11` pointing to a writeable area of the snap (e.g. `$SNAP_
- on first run, copy the common PKCS modules to that writeable area
- document that custom modules (and their dependencies?) should be manually copied to that directory
- create a new interface (not auto-connected, that's okay) for access to `/var/run/
I'm not familiar with how smart card readers work though, so feedback and suggestions are welcome.