On Tue, 9 Aug 2011 22:31, gn...@lists.grepular.com said:
gpg: verify CHV1 failed: general error
gpg: signing failed: general error
gpg: [stdin]: clearsign failed: general error
I suggest that you use gpg2 and not gpg. You should also update GnuPG
to at least 2.0.17. 2.0.14 is quite
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
On Wed, 10 Aug 2011 11:23, gn...@lists.grepular.com said:
2011-08-10 10:16:02 scdaemon[5153] DBG: response: sw=6581 datalen=0
Ooops,
SW_EEPROM_FAILURE = 0x6581,
it may be that you had no luck and got a faulty chip. Contact the
supplier for a replacement.
Or did you run a series of
On 10/08/11 11:38, Werner Koch wrote:
2011-08-10 10:16:02 scdaemon[5153] DBG: response: sw=6581 datalen=0
Ooops,
SW_EEPROM_FAILURE = 0x6581,
it may be that you had no luck and got a faulty chip. Contact the
supplier for a replacement.
Or did you run a series of automated tests
Hi,
My OpenPGP Card (v2) has been working fine for a couple of days now, but
it has stopped tonight.
Simply trying to sign some text gives the following error:
mike@Fuzzbutt:~$ date|gpg --clearsign
-BEGIN PGP SIGNED
