> Well, there is a need for a system(s) that handles > 1) Guessable keys > 1a) Spam > 1b) Valid clashes > 2) Updating
Maybe, maybe not. I'm not yet conviced that "guessability" needs to be built into any function of the server--I think clients can do that. They can implement other naming schemes as well. All SVKs give you is the ability to have a reliably locatable, author-updatable document. What it gets used for and how it is found are issues for later, but we might as well build that part of the infrastructure now. > > So the decisions to be made: what algorithms to use, > > For the hash it depends on how pained people are about the speed of MD5. > If we really want the speed then MD4 is quicker (but less secure) MD5 isn't very secure either. SHA is, I think, the current gold standard for such things. Hal, you're the cypherguru here (and the only one with a PGP key older than mine:), what are your thoughts on best algorithms for CHKs/SVKs? -- Lee Daniel Crocker <lee at piclab.com> <http://www.piclab.com/lcrocker.html> "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
