[cap-talk] On revocation and the use of wrappers andIn Defenseof Identities
Marcus Brinkmann
marcus.brinkmann at ruhr-uni-bochum.de
Sat Dec 9 14:39:58 CST 2006
At Thu, 7 Dec 2006 11:49:57 -0600,
"Karp, Alan H" <alan.karp at hp.com> wrote:
>
> > > The server can always refuse if a given capability has been
> > delegated
> > > too many times.
> >
> > As Neal said. Or: "What's too many?" [1]
> >
> That's a policy decision on the part of the server.
But the server can not make a meaningful policy decision here. It's
both the wrong party to allocate the resource and the wrong party to
manage the resource allocations.
> If the choice is
> denying this delegation or crashing and denying all service, the choice
> is obvious. In Client Utility each client had a quota that set a limit
> on how much of the server's storage that client could use. Each
> delegation consumed storage that was charged against that quota.
> Reached your quota? Delegation denied. If that meant you couldn't get
> your work done, tough.
I would like to have an operating system in which people can get work
done.
Thanks,
Marcus
More information about the cap-talk
mailing list