GNUpg

[gaf at blu.org (Jerry Feldman)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

Yes, I upgraded from 1.06 to 1.21. My key is now verifying correctly. 
Trutdb has been rebuilt.
BTW: Your key is expired. 
mike ledoux wrote:

> Let me guess.  You upgraded from 1.0.6 or earlier, right?
> 
> You need to tell GPG that your key is trusted; 1.0.6 and earlier
> implicitly trusted any key for which you had the secret key available,
> 1.0.7 and later fix this bug.  Run 'gpg --edit C5061EA9', type 'trust'
> at the 'Command>' prompt, and then '5' to 'ultimately trust' your key.
> Type 'save' at the 'Command>' prompt, and this problem should go away.
> 
> You should also run 'gpg --rebuild-keydb-caches', as the cache format
> changed after 1.0.6.  It is probably also a good idea to run 'gpg
> - --update-trust' to make sure your trustdb is in a reasonable state.
> 
> - -- 
> mwl+blu at alumni.unh.edu             OpenPGP KeyID 0x57C3430B
> Holder of Past Knowledge           CS, O-
> Put your wasted CPU cycles to use: http://www.distributed.net/
> "After the first death, there is no other."  Dylan Thomas
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> Comment: Get my public key from http://www.volta.dyndns.org/~mwl/pgpkey.asc
> 
> iD8DBQE+FeHu5rgdHFfDQwsRApv0AKC9nJEE8+9UhuZ4xjQd/PbrZpzP1wCeOrbv
> 0BBFnFYibLKK6s+cZbnwreI=
> =ue8F
> -----END PGP SIGNATURE-----
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss
> 

- -- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 12/25/2001

iD8DBQE+Fe3E+wA+1cUGHqkRAqETAJ9QSYCMtEC5J4gJ0INniutVL0QIDwCdFgae
ho571oTabFVSAkmqzdpeBuI=
=M8jk
-----END PGP SIGNATURE-----