Upgrade from 1.0.4 to 1.4.6

[Robert J. Hansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

SeidlS at schneider.com wrote:
> existing key rings.  We are getting errors that gpg is questions whether
> the keys actual belongs to the person named in the user ID.  We have run
> the --rebuild-keydb-caches, but are still getting that error.  Can anyone
> provide some input on what we need to do to fix this issue?

If you want to do a brute-force-and-ignorance approach, you can add

"trust-model always"

... to the end of ~/.gnupg/gpg.conf.  Please do this only if you have
confidence in all the keys on your keyring.

Also, if memory serves GnuPG changed the way it handled options between
1.0.4 and 1.4.6.  Configuration options are now stored in
~/.gnupg/gpg.conf, not wherever they were stored before.  It might be
worth checking to see if your gpg.conf file exists, and if so, what's in it.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBCAAGBQJFr7E1AAoJELcA9IL+r4EJ3Z0H/3Y7YbF9vDbr9qW2ozEmfpvJ
Df+29LebpIWSQUQbJT2ymY95P+iifs6r4lLITRfQ/7Zg5cVadBpt4dxT8bZdF+ff
ayd/jGxpFHV0SV02gwDUCyVk4LS7wSFeTNzfjT6WTba9Zap/+5GZR7te0yzlvPmg
MCms166hzmlahIkGRK/7v+IkSViOHSDB43HEDDrlnTtMy5IVH4FrXyhscVNBmRy5
rCPNFnyZvY5kbFKlj+Irk7xMB88Adoyghd5UbRTCzYQoH93R2eK6hGhHrvyYJvPH
m+/TuPt6bh3OUwlthZgmEhx++08ppW0GAEURvbwzmatplXuqI15pRCwoBsx4yD0=
=ptkz
-----END PGP SIGNATURE-----