I think that rate limiting new or updated keys may be a good idea. My keyserver currently recieves about 50-150 keys every hour, limiting this to something like 300 keys in 10 minutes may help.
Am 26.05.16 um 09:42 schrieb Pascal Levasseur: > The administrators of the SKS servers should be able to choose the level > of complexity of the proof of work using a parameter in the SKS server > configuration file. > > Using this parameter they could adjust the complexity of the proof of work : > > - to the inevitable increase of performance of CPU/GPU, > > - to quickly react by increasing complexity if SKS servers are under > "attack". > > Pascal > > Le 25/05/2016 18:31, Christian Felsing a écrit : >> Am 25.05.2016 um 18:13 schrieb Valentin Sundermann: >>> Hi, >>>> Can we add a proof of work mechanism to make adding a key to the server >>>> more "costly" ?. >> >> >> Let client solve a simple integer factorization of a random number given >> by server with e.g. 64bit build from two prime numbers. Client has to >> find those prime numbers. Until "Can integer factorization be done in >> polynomial time?" is answered with "yes" this can be seen as a "hard >> problem" so even quite powerful cpus will need a few seconds to solve that. >> >> Christian >> >> >> >> >> _______________________________________________ >> Sks-devel mailing list >> Sks-devel@nongnu.org >> https://lists.nongnu.org/mailman/listinfo/sks-devel >> > > > > > _______________________________________________ > Sks-devel mailing list > Sks-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/sks-devel >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
