we have an app that uses pcsc to connect to smartcard readers. This works as long as we don’t try to install via the snap store. If we go through the store the connection attempt fails with errors.
I don’t know why pcsc-gscriptor works with an almost identical setup … I suppose autoconnecting the interfaces also does something to the permissions.
By the way, there are other threads on this forum addressing similar issues, but they are not solved in a way that is feasible for us. We don’t want to ship pcsc-daemon or any drivers for licensing reasons.
Sorry of this gets boring as I document my learning journey here, but if I include the content interface of another snap, dies it mean that when I run my snap, then LD_LIBRARY_PATH gets replaced inside my app’s sandbox so that the application loader will automatically find the library you have compiled for your snap?
In other words: Will my app loader load your snap’s dynamic lib instead of the default one that Linux/Ubuntu has installed?
Because if not, then I cannot use your socket, can I? Because I still load the default lib and then it wants to access /run/pcscd/pcscd.comm.