dougb at FreeBSD.org
Tue Sep 29 18:00:13 UTC 2009
-----BEGIN PGP SIGNED MESSAGE-----
FYI, cross-posting to more than one list is discouraged.
J. Hellenthal wrote:
> On Wed, 23 Sep 2009 11:40 -0000, jhellenthal wrote:
>> If you do not need to pgp/gpg sign email message to the lists please
I think a lot of people would define "need" differently than you do.
Part of being on a public mailing list is dealing with traffic in
formats that you don't necessarily like or would choose to use. The
robustness principle fits here, "Be liberal in what you accept, and
conservative in what you send."
>> I know I probably don't have your pgp public key and a lot more
>> users probably do not either.
There are ways to address that problem. I see that you're using
Alpine, not sure what you're using for PGP in association with that.
My own mail/pine-pgp-filters port works quite well for this purpose.
You can also include the following in your gpg.conf:
which will retrieve the keys for you without intervention. (FWIW, I
also recommend the options no-include-revoked, import-clean, and
Personally I keep the keys that I care about in their own keyring
files, and allow the "random" keys to be imported into pubring.gpg.
That way I can nuke that ring, or keys on it any time and know I'm not
losing anything important. I'll leave that configuration as an
exercise for the reader. :)
> If I do not have your public key in my keyring then I do not want it, do
> not need it and have no use for it at this time. This keeps my keyring
> small and manageable.
Well yay for you! :) However explaining your reasoning isn't making
you sound any more reasonable. The "public" part of "public key
cryptography" is often messy, you need to learn how to deal with it.
Doug (who signed this message so everyone would know it's from me, no
This .signature sanitized for your protection
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)
-----END PGP SIGNATURE-----
More information about the freebsd-ports