public keyring management practices (was: Re: GPG Recipients
List)
Douglas F. Calvert
dfc at anize.org
Wed Dec 3 23:35:33 CET 2003
On Wed, 2003-12-03 at 18:57, David Shaw wrote:
> On Wed, Dec 03, 2003 at 11:04:19PM +0000, Neil Williams wrote:
>
> > Lengthy trust rebuilds do slow down the email client with new keys
> > and also slow down KGpg when it opens. However, another reason is
> > refreshing keys - you can't be sure about a key not being revoked
> > unless you refresh it so I refresh quite often. Certainly before I
> > verify packages or encrypt messages to occassional contacts.
>
> I've occasionally toyed with making an option to automatically do a
> refresh before encrypting, and a different option to automatically do
> a refresh when verifying. I haven't done it because the load on the
> keyservers would be brutal. I'd be curious if someone has a different
> take on that, or how they would want such a feature to work.
What about a keyserver that only handles revocation certificates? Does
anyone know how many revocation certificates are on the keyservers? And
how many get added per week?
--dfc
Douglas F. Calvert
http://anize.org/dfc/
GPG Key: 0xC9541FB2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : /pipermail/attachments/20031203/2cc70692/attachment.bin
More information about the Gnupg-users
mailing list