> Under your proposal what would stop a malicious node from sending > updates as quickly as possible to flood the network?
That's not an issue with SVKs: remember that they are, by their very nature, cryptographically signed. That means it's not possible to "flood update" someone else's document since servers will just discard invalid signatures, and if someone wants to flood his own documents, nodes may choose to just ignore the nym. That won't prevent a one-time DoS, but then nothing will anyway. I do have a suggestion, though: to truly prevent any possible "explosion" effect, the "fireworks" sent from each node on the update path where the document was found should have an HTL of 1, or just possibly 2, and nodes must not further distribute any received update message with an HTL of 2 or below. In other words, only flare from the main branch, so it's not so much a broadcast, or even a deep probe, so much as a "thick" probe. -- Lee Daniel Crocker <lee at piclab.com> <http://www.piclab.com/lee/> "All inventions or works of authorship original to me, herein and past, are placed irrevocably in the public domain, and may be used or modified for any purpose, without permission, attribution, or notification."--LDC _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
