> This seems like a more flexible idea that our current owner-signs-update > model. To create a publically-writeable subspace, for example, insert a > special file named ACL which says that anyone can create a new file but not > overwrite an existing one. This gets around the cryptographic weakness of > using a private key as the SVK key, and prevents people from overwriting > each other. The downside is that you'd have to retrieve the ACL each time > you wanted to verify a file.
I think that this would be better handled client-side. A user can download a subspace's ACL list or whatever other sort of permissions system client writers feel like using. The client can then ignore files which don't work with the ACL list. The matter is simplified by the fact that the only operation possible is to add a file. All other operations, such as deleting files or replacing them, would have to be handled by inserting files which specify that such an operation should occur. I have yet to see an application which needs node-side permissions more complicated than signatures. _______________________________________________ Devl mailing list Devl at freenetproject.org http://www.uprizer.com/mailman/listinfo/devl
