auto refresh-keys
MFPA
expires2010 at ymail.com
Sat Jun 19 14:27:23 CEST 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi
On Friday 18 June 2010 at 8:42:31 PM, in
<mid:67BE2DF6-B832-4D0C-B176-F1C93986B92F at jabberwocky.com>, David Shaw
wrote:
> When I wrote the new keyserver stuff, I thought about
> this sort of thing, but the lack of a good way to store
> metadata was a problem (the keybox fixes this), as well
> as the concern that keyservers are effective trackers
> of who is using what key. For example, a keyserver
> operator could tell (based on how often which keys were
> refreshed), who your encrypted correspondents were, in
> rough frequency-of-communication order, to boot.
The potential tracking could be mitigated against by an ability to
configure a list of keyservers rather than just one, and using a
random selection from the list for each keyserver operation.
- --
Best regards
MFPA mailto:expires2010 at ymail.com
Can you imagine a world with no hypothetical situations?
-----BEGIN PGP SIGNATURE-----
iQCVAwUBTBy3sqipC46tDG5pAQrEUAQAkYQPp0jqsibnojxiEZZEFUpVcN/4YT+/
31xL1ySP+kqlu1XD0/ReoYhkLlfKofCIfGKNDl0/SVvk/hEBlp3TMRFKWPBEpeFP
l6+Lh0elIIP8z3fUBELX/kSPkrtSlHyjSpUbFHz3BFvgFBqni/NCOQ2WI3dVju1O
n30mZ7qtUUU=
=InoV
-----END PGP SIGNATURE-----
More information about the Gnupg-users
mailing list