On Sat, Feb 24, 2001 at 09:10:37PM +0000, Theodore Hong wrote: > Anyway, they control permissions for updates by associating to each file a > certificate signed by the owner saying "use access control list X" for this > object, where X can be some default setting or another file. An entry in > an ACL consists of a granted permission level plus the grantee's public > key. > This seems like a more flexible idea that our current owner-signs-update > model.
My original subspaces proposal was even more flexible than this. You would write a stack-based language (called SeSiL - SubSpace Language) which would decide whether a particular document would be permitted within the subspace. This could be as simple as checking that it was accompanied by a valid signature (same as current subspaces), or much more complex, such as allowing subspace-owners to deligate subspace permissions, or restricting the contents of documents in some way. This proposal was deemed too complex by the other core developers, and the current solution was the compromise we reached.... ho hum. Ian. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20010226/c6a7cb02/attachment.pgp>
