I can't say I like the current (AFAIK) notion of being able to overwrite the contents of a document with an update. What about something like this:
A user inserts a document consisting of a a key and data (as usual), as well as a signature by a nym. The server holds on to this signature for the life of the data. When the user wants to "update" the document, (s)he submits a signed message containing the public key, the old KHK, and the new Key, the latter of which is encrypted with the old Key. The server retrieves the old document, verfies that it came from the same nym that submitted the update message, and when it is satisfied as to the authenticity of the update message, it simply attaches the new Key (encrypted, remember) to the document and forwards the update message to any server it thinks should care. Now when a request is made, both the new Key and the data are returned, and the client can decide whether it wants the old version or the new version. Thoughts? P.S. Does there exist a specification of the FreeNet network protocol besides the source? My Java ain't so hot. -- Drew Bloechl drew at cesspool.net PGP key ID: 33855516 _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
