[Sks-devel] How much load are keyservers willing to handle?

[adrelanos]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

I am planing to write a script, which will refresh the apt signing key
before updating using "apt-get update". I am certain, that mechanism
doesn't exist yet. [1] The script might get accepted in Debian. [2]
With my Whonix hat on, it's safe to say, that this script will be
added to Whonix (which is a derivative of Debian).

Writing that script would be much simpler if it could re-use the
existing keyserver infrastructure. Now imagine if this gets added to
Debian, that all users of Debian and all its derivatives will always
refresh their signing key against keyservers? Could keyservers cope up
with the load?

Other than asking in general, (not everyone can speak for everyone) it
may be better to ask:
Would you accept that kind of traffic on your keyserver (pool)?

The legal question would be interesting, but don't worry, if you ask me
not to use keyservers for this, I'll use a mechanism outside of
keyservers.

Cheers,
adrelanos

[1] http://lists.debian.org/debian-security/2013/10/msg00065.html
[2] http://lists.debian.org/debian-security/2013/12/msg00031.html

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

iQJ8BAEBCgBmBQJSsmw/XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5QjE1NzE1MzkyNUMzMDNBNDIyNTNBRkI5
QzEzMUFEMzcxM0FBRUVGAAoJEJwTGtNxOq7vx0kP/0glaextuqbrcUekAjCguLJm
0hclCbvFRUyfhGENwaI3zo4qBlrW0ukpqOkQWRJB4Tz+ryyOlNhZClvZ8OG5yeXl
osjw5IASQtzSOFLNOhzDagbIypvQg9o+JvFtKGzB8xQcLEq3ZX1x1yNd1XrGjQxO
/RSYmfySQ2hkvJA3yG/t9WN3tV/8wDu4M7Zqkv5g7fpkKvZ8tBEf1cK5pVsAl1jU
Lo5sH1aYwSRUsCTrP0cJjX+I6D4ltrqU+97QQ7Cl5xDJszcKglADzUAJtwEKfNrm
KXxU3O/RpUQTWDpxzwGz3wSelRXoOokLkm+c8VsRDrpXiljaz1hEqgWcHkpPdwfU
FCGq1N5OGofC4DzblRCS9USaOKhIMenUr2xCRGBr8lt/msDmyQXWD2f1wOJf5yT1
pEmJu1tXtA/5nOeEBHeFwd7ooj+hFmeQotYTI646wjev3vKQj8TwDMYeRf658veC
rlYXgfkuEAjipX/vjSwUXXqMYEugGVw90kT8JuGAcbJ/Ac8Pc0zFmIr7noVzl79B
GC3RiIgV8XILs40bAoNl8uLk1CsJdbdA8XdiKcNicTWo6q9wQ/iUxvKDpCFRZIkh
n0UFNNwdCts13WTwpr1+9QnMd9PhKOch56xNexTldqcbHAobtsGri0bGSErChEua
stEZMZLylt9rnOX6CFlz
=hc6e
-----END PGP SIGNATURE-----