Re: scdaemon needs restarting after removing OpenPGP smartcard
On Tue, 5 Jun 2012 15:01, klaus.la...@gmx.de said: I found ticket https://bugs.g10code.com/gnupg/issue1238 which describes this error. Are there any plans to downport the fix described in the ticket to 2.0.X. I am currently backporting the SCD changes in master branch to 2.0. For this particular issue, I believe that it has been fixed by the following commit, which was included in 2.0.18 already. commit 576de6e539646f021dafff8d4e3327c115a51ad4 Author: Werner Koch w...@gnupg.org Date: Tue Jan 25 22:03:16 2011 +0100 Fixed problem with unplugging card readers. From Grant Olsons's mail to gnupg-devel@: This is three-quarters NIIBE and one-quarter me, but I though it would be easier to have a single complete patch that applies to STABLE-BRANCH-2-0 than two patches floating around. This is basically NIIBE Yatuka's patch here: http://lists.gnupg.org/pipermail/gnupg-devel/2010-November/025828.html Plus another check that closes down the reader explicitly if we get a SW_HOST_NO_READER error, so that an unplugged reader doesn't hold onto the first slot, preventing us from getting to the active plugged reader. -- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: scdaemon needs restarting after removing OpenPGP smartcard
On 2012-06-05 at 17:55 +0200, Werner Koch wrote: gniibe: You reported a couple of other possible problems. Do you thing we should go after them for a 2.0.20? My changes are basically two areas in master branch. (1) Fix of ccid-driver.c for partial support of extended APDU. This was needed for Gnuk ( version 0.16). (2) Pinpad input enhancement for passphrase modification. Besides, I know there is a problem in scd_update_reader_status_file, which was repoprted the other day, but I haven't fixed yet. I think that access to the object of struct slot_status_s should be locked. I'll lock into those for backporting. -- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
scdaemon needs restarting after removing OpenPGP smartcard
Hi, when I remove a cryptostick and try to access it with i.e. gpg2 --card-status I get an error gpg: selecting openpgp failed: ec=6.32848 gpg: OpenPGP card not available: general error In this case scdaemon log shows scdaemon[4167]: chan_7 - SERIALNO openpgp 2012-06-05 14:35:39 scdaemon[4167] PC/SC RESET failed: invalid value (0x80100011) scdaemon[4167]: chan_7 - ERR 100663404 Card error SCD scdaemon[4167]: chan_7 - RESTART scdaemon[4167]: chan_7 - OK I found ticket https://bugs.g10code.com/gnupg/issue1238 which describes this error. Are there any plans to downport the fix described in the ticket to 2.0.X. Thanks, Klaus signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: scdaemon needs restarting after removing OpenPGP smartcard
On Tue, 5 Jun 2012 15:01, klaus.la...@gmx.de said: I found ticket https://bugs.g10code.com/gnupg/issue1238 which describes this error. Are there any plans to downport the fix described in the ticket to 2.0.X. The fix seems to be this: commit 2d91febbd8d30beb7eb33f7aa80ffd5691d1d3cc Author: Werner Koch w...@gnupg.org Date: Wed Dec 14 10:30:01 2011 +0100 scd: Fix resetting and closing of the reader. * scd/command.c (update_card_removed): Do no act on an invalid VRDR. (do_reset): Ignore apdu_reset error codes for no and inactive card. Close the reader before setting the slot to -1. (update_reader_status_file): Notify the application before closing the reader. -- With this change the scd now works as it did in the past. In particular there is no more endless loop trying to open the reader by the update_reader_status_file ticker function. That bug basically blocked all card operations until the scdaemon was killed. However it won't apply directly because we changed other things in 2.1 as well. We should port it back. gniibe: You reported a couple of other possible problems. Do you thing we should go after them for a 2.0.20? Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users