Re: Access Control Draft
On Mon, 19 May 1997 email@example.com wrote:
> a silly question perhaps (excuse me if this has been discussed previously):
> is there some reason why something vaguely like the "certificate"
> systems being used in electronic commerce couldn't work in this
> context? That is, the "document-set-owner" issues "tokens" to
> authors who need to be allowed to access/modify documents in the
> set. When one of those authors wants to "check in" a modified
> document or document-part, he or she must be able to accompany his
> work with the proper "token".
Not that I can think of. In fact, one example that comes to mind is the
standard file system for Amoeba (a distributed operating system). In many
ways, it reminds me of HTTP (immutable files and such), and uses
essentially this scheme for file access. Basically, the file server
(called the "bullet server" in Amoeba) issues what it calls capabilities
which are then required for file access. I quite like this idea.
> Note: I'm not saying anything about the complexity of the token, nor the
> protocol for issuing or recognition nor any of the details.
> I'm just sketching a model.
I understand. The basic architecture and the security model are more or
> Howard S. Modell
> Adv.Computing Technologist/2 POBox 3707, m/s 4A-25, Boeing D&SG
> firstname.lastname@example.org Seattle, WA 98124-2207
> http://warlok.ds.boeing.com/~howie/ (206)662-0189[v] (206)662-4018[f]
email@example.com / http://www.wnetc.com/home.html
If you're going to reinvent the wheel, at least try to come
up with a better one.