Before upgrading to gnupg-1.2.1-4 through RHN, issuing this command: gpg --verify anyfile.tar.gz.sig anyfile.tar.gz would usually get me an answer within a few seconds. Now, gpg simply hangs by its toenails and sits there. Here's an example: [rlc@xxxxxx rlc]$ gpg --verify gnupg-1.2.2.tar.gz.sig gnupg-1.2.2.tar.gz gpg: Signature made Thu 01 May 2003 11:10:15 AM EDT using DSA key ID 57548DCD [User presses ctrl-c at this point] gpg: some signal caught ... exiting [rlc@xxxxxx rlc]$ rpm -q gnupg gnupg-1.2.1-4 I also get this result less frequently: [rlc@xxxxxx rlc]$ gpg --verify gnupg-1.2.2.tar.gz.sig gnupg-1.2.2.tar.gz gpg: Signature made Thu 01 May 2003 11:10:15 AM EDT using DSA key ID 57548DCD gpg: [fd 6]: read error: Connection reset by peer gpg: can't get key from keyserver: eof gpg: Total number processed: 0 gpg: Can't check signature: public key not found I also notice that verifying digital signatures in Evolution (by clicking the "lock" icon in a given email) doesn't seem to work either; one gets messages similar to the 'Connection reset' message above. Is anyone getting this problem? Thanks, Bob Cochran Greenbelt, Maryland, USA
Attachment:
signature.asc
Description: This is a digitally signed message part
