[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mutt, gpg and automated key retrival

Hi Andreas!

Andreas Tille schrieb am Montag, dem 25. September 2000:
> I have the same options set (except  keyserver pgpkeys.mit.edu, but
> the problem will be the same) and use pine with pgp4pine.  When
> trying to obtain non-developer signatures (the developer keyring
> is installed on my machine) I get the following:

> ------------ Output from gpg ------------
> gpg: Schlüssels D644D71A von pgpkeys.mit.edu wird angefordert ...
> gpg: failed to create temporary file
> `/usr/share/keyrings/.#lk0x80cf438.wr-linux02.30142': Keine Berechtigung
> gpg: fatal: can't allocate lock for `/usr/share/keyrings/debian-keyring.pgp'
> secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/16384

> May be it is the same problem in your case that gpg wants to write to
> /usr/share/keyrings/ a temporary file and isn't allowed of course.
> I havn't found a way to avoid that.

No, the set pgp_verify_sig=yes solved Andreas S.' problem. Your problem
seems to be that you specified keyrings in your ~/.gnupg/options
but don't have write access to them.

I suggest adding a "keyring ~/.gnupg/pubring.gpg" (or whatever your
personal public keyring is called) as the last keyring option in the
config file.

gpg will then import new keys into that keyring which should work. You
still cannot update keys in other keyrings though.


Reply to: