On 10/08/11 08:49, Werner Koch wrote: > I suggest that you use gpg2 and not gpg.
I have now done this. > Let's debug it. Please put the lines > > verbose > debug 2048 > log-file /foo/scdaemon.log > > into ~/.gnupg/scdaemon.conf and kill a running scdaemon. Then run your > signing command again. In the log file you should find output similar > to this: > > scdaemon[17805]: DBG: send apdu: c=00 i=20 p1=00 p2=81 lc=6 le=-1 em=0 > scdaemon[17805]: DBG: raw apdu: 00 20 00 81 06 3x 3x 3x 3x 3x 3x > > This is a command as send to the card. The c=00 i=20 indicates the > verify command which fails for you. If it works the next line would be > a > > scdaemon[17805]: DBG: response: sw=9000 datalen=0 > > However your SW will be different. What is it? 6581: 2011-08-10 10:16:02 scdaemon[5153] DBG: response: sw=6581 datalen=0 Regards, -- Mike Cardwell https://grepular.com/ https://twitter.com/mickeyc Professional http://cardwellit.com/ http://linkedin.com/in/mikecardwell PGP.mit.edu 0018461F/35BC AF1D 3AA2 1F84 3DC3 B0CF 70A5 F512 0018 461F _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
