On Sat, 2004-11-20 at 11:49 -0600, Robert G. (Doc) Savage wrote: > On Thu, 2004-11-18 at 17:47 +0100, Alexander Dalloz wrote: > > Am Do, den 18.11.2004 schrieb Paul Howarth um 10:02: > > > > > > Back again with (probably) another configuration nit. Since upgrading > > > > from FC1 w/Evolution 1.4.2 to FC3 w/Evolution 2.0.2, I've noticed that > > > > all the digital signatures on this list are now flagged as invalid. I > Thanks for your replies. Very helpful. Now that I look in my home > directory, I find that there is no ~/.gnupg directory, ATM, you are supposed to create it. > and of course no > gnupg.conf file to modify or lock. > > When I click on that "Invalid signature" icon the Security Information > popup box says: > > Digital Signature > The signature of this message cannot be verified, it > may have been altered in transit. > gpg: failed to create temporary file `/home/doc/.gnupg/ \ > .#lk0xf7005ac8.lioness.7077': No such file or directory > gpg: can't allocate lock for `/home/doc/.gnupg/pubring.gpg' > gpg: keyblock resource `/home/doc/.gnupg/pubring.gpg': general \ > error > gpg: armor header: Version: GnuPG v1.2.6 (GNU/Linux) > gpg: Signature made Thu 18 Nov 2004 10:47:55 AM CST using DSA \ > key ID B366A773 > gpg: Can't check signature: public key not found > Encryption > This message is not encrypted. Its content may be > viewed in transit across the Internet. > > That's heavy stuff. By upgrading from FC1 to FC3, have I missed some > sort of pre-config routine that should have been run after gnupg was > installed? The message above is gpg's way to tell you that you missed to create "~/.gnupg" mkdir ~/.gnupg should help. Ralf
