> Try the diagnosis output, sometimes it tells you more.
>
> gpg2 -vvv --debug-all --debug-level=expert
The 'expert' setting didn't seem to tell me enough so I tried the 'guru'
option on two different machines and noticed that the Arch Linux machine
seems to use two slightly different strings whe
Many thanks for the reply, Werner.
> What version of Libgcrypt are you using? "gpg2 --version" shows that.
libgcrypt 1.6.1
> Is that an intermittent problem which always happens on the same machine?
Yes. I can run a command such as "gpg2 --clearsign doc" and it will
fail with the "Bad signatur
Thank you for the response, Peter.
> Did you overclock your computer? You might need to lower some setting if
> you did.
I haven't overclocked the computer but it is only a (quite old, now)
Acer Revo
with an Intel Atom 230 1.6 GHz CPU.
> You could try memtest86+ for several hours.
I will try th
The plot thickens.
I have just generated a new keypair on the Arch Linux box where I'm
having the problem and I can use this new key (repeatedly) to "gpg2
--clearsign doc" and it works every time.
So, it seems that the 'Bad signature' issue is related solely to my
'primary' key, which would sugge
Hi
Firstly, my knowledge of GPG is very weak and I am not a UNIX administrator, so
my access and knowledge are rather limited.
I have been asked to set up file encryption / decryption of files transferred
between our SUN OS servers and two customer's servers.
One customer is using a basic 2048 s
