Re: [Sks-devel] Syncing Keybase to SKS

[Brian Minton]

I think spreading out the load seems reasonable. I don't know how the pool maintenance scripts would handle one server suddenly having 40k more keys.

On Mon, Aug 3, 2015, 12:58 AM Daniel Roesler <address@hidden> wrote:

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

Howdy all,

I have been working on project to sync Keybase and the SKS
keyserver pool. As I'm sure many of you know, Keybase has
seen a fair amount of adoption, and I'd like to make sure
those users' public keys are available to be found when you
run gpg --recv-key. Hopefully, the result will be to keep the
the user-friendliness of Keybase while still making their
public keys backward compatible and available to gpg.

Luckily, Keybase uses a merkel tree, so it will be fairly
straightforward to scan the tree and find the public keys
that are missing from the keyserver pool. There's about
47k total public keys, and I'm assuming about half will be
new keys to sks (will post again with exact figures once
my script is fully operational).

My question is how should I insert the missing keys into
the pool? Should I submit them to my keyserver and let
them spread over gossip, or should I just POST them to
the round robin domain to spread the inserting around?
How long of a period of time should I take to insert ~20k
public keys?

After the intial sync, it shouldn't be hard to update in
an ongoing basis. I plan on doing the initial sync
sometime later this fall or early winter.

Hooray for more user-friendly public key infrastructure!

Daniel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVvvLCAAoJEOf2+tFy7+49TGMP/3CNtslR2bWV1BRdbNK+DuUk
rzYnouppdKju++B73KKGtuMGY2PKQK3UDwlG/b9Iy6J3mU8P3sFwVeYpnXWQvVFH
PihpqYNguaK21eQ7i+1MmBoM1rKYspoHiQFvhqCR2yYxIsoO4QaKyYWZtdlASUBS
jaFRiJN7IogLJ3oN8GzTkytJ/Y7wBgmZqa5tniXEeZIgjWh1fn9DfDDLG7dLPt2L
E/q+nNIM5p7+E4RAqy4AKwS5LE7NXb7/5zN0EzEDiPu5z8i76PW3kmx7YhS4joHt
d+c5/AeXB1AGE2s5BSsCzZsTtnPkBEWmOi99ZwL7axHdI47yj6KAGnmtFK5qXtZM
57hcIN4/M2J+u4gjrTYXPcJhg5cSklS9ZAbMgLPDYmmHRoOW601wZMIWRa2/Z0TB
1kefZ6WQ3uRJ8Hb8erpZyk7pWYg7m06EoxPELQYrMIQdI+zJYFQ8DkEKQsdO/dMA
ZUfhXqCM1bv6zMhFV1DktjbI1Z6ZWUwY37mortbCbR6zYM+UM8ooBqrOq3TEpen5
x25ztDniyGZd/G9Suieqc+ChorbKGmIy9dBAjY+cOYPgD3+gMP+bow1o4Hk3GTfw
evgDm4buSv7TbYvEa1F0tyRDB4jb4IlFigKa9Txo7jR6UyshMm/aoCPb6P11Xt2x
3ShnCHDVzPPnZ7lVLfWn
=hNYx
-----END PGP SIGNATURE-----

_______________________________________________
Sks-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/sks-devel