-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I agree with this. Versioning would also make a replacement attack far less
> effective. Because someone could make a new version of a file, but can't
> delete old versions of the file, if someone realizes that the new version is
> bogus then the bogus version can be replaced with a newer version based off
> an older version. Adding versioning would require that the protocal be
> changed so that new version messages would be transmitted from a node to
> other nodes telling the other nodes that a new version is availiable.
> Without such a change, other nodes would use an older version of the file
> because they don't know that a new version exists.
I agree. We had a proposal for a document stack not too long ago. It
would work like this. Someone would request the KHK of a document, which
point to a freenet document of the following format:
TimestampN CHK
.
.
.
Timestamp1 CHK.
This should actually not be a KHK, but a specific type of KHK where
updates are allowed only to add one line to the front of a document. This
would be handled by the node.
On update, Alice inserts the CHK value under the modified KHK. The insert
request propogates until it finds the document stack. If it doesn't find
it, its an error. If it does, the Node places the current time and the
new CHK on the top of its entry.
Scott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5EOMXpXyM95IyRhURApr/AJ9mdbwIAhyiHO893cA6yRbqKMVVTgCgnOeY
OICbGtIiXNlwz3QgKJXA1iw=
=c5fX
-----END PGP SIGNATURE-----
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
