Re: pgg doesn't seem to like me

[jam@jamux.com (John A. Martin)]

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

>>>>> "Simon" == Simon Josefsson
>>>>> "Re: pgg doesn't seem to like me"
>>>>>  Sun, 06 Oct 2002 02:03:35 +0200

    Simon> Uhm, are there any other outstanding PGG problems?  [...]
    Simon> Or PGP/MIME and S/MIME problems in general?

Another point perhaps.

When verifying, gnus/pgg, or someone, will sometimes prompt with
something like:

        Key ... not found; attempt to fetch it (y or n)

When I say "y" it fails because my system is not set up to allow any
random process to willy-nilly access any random outside entity.

When I say "n" verification generally succeeds because my setup
provides for gpg to fetch keys from a particular keyserver.

I believe this is a reasonable set up and perhaps a preferred set up
in most situations.

I have not found where to disable gnus from attempting independently
to determine whether to attempt to fetch keys.  Presumably gnus key
fetching can be gracefully disabled, but a larger question is why
should gnus want to do this?  And by default no less?

Gpg has had workable key fetching for a long time.  Key fetching was
substantially improved in gnupg-1.0.7 and much improved again in
gnupg-2.0.0.  Gnupg is committed to coordinating key fetch with the
improvements under way with many public key servers.  IIRC more key
fetching improvements are slated for gnupg-2.0.1.  This is to suggest
that users would be better served were gnus to let default key
fetching be left to the user's gpg and optioned by ~/.gnupg/gpg.conf.

HTH

        jam

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAj2iPtgACgkQUEvv1b/iXy/L2gCfQ8HV5U7S+PZLEkYS+TwWDosw
ZXsAnA0Ti2LJ34kgI1k2++enEP2eiUHs
=I9Ot
-----END PGP SIGNATURE-----