I think the problem is that gpg2 is not the one doing the smartcard calls. It spawns a gpg-agent process, which then spawns an scdaemon process. These two are still running when you're back at the command prompt.
gpg does not do this by default, it talks to the card directly. However, after gpg2 has spawned its helpers, these helpers are still alive, and *holding the card reader exclusively*. So now gpg can no longer access the card reader because scdaemon, running in the background, already has it open. I don't know /anything/ about SELinux. But hopefully now you can look in the right place, because I think you got sidetracked by the gpg2 process not actually doing the business. HTH, Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
