If your intent is to let your teenager drive the car to the store during
daylight hours, then you've got provide a way to undo the lock. And,
in fact, you never set the lock in the first place, you just left the
car in the driveway and need to put a note on it saying who could
drive it, where and when.
There's no trust model today for HTTP content mods; OPES will take
a big step forward in defining the model and mapping it to an
actual implementation.
Hilarie
Bernard Aboba <aboba(_at_)internaut(_dot_)com> 07/10/01 12:42AM >>>
Agree on the lack of authentication and authorization issues, these are 2
items OPES is proposing to address. Several of us have long believed that
with an OPES framework, multiple existing remote procedure call
protocols including iCAP and SOAP can be added to an authenticated and
authorized intermediate proxy model. By applying AAA in the form of an
Admin Server, where authorization is classically a policy model with PRC
modules and the like and authentication is capable of using protocols
such as SSL, we have the opportunity to disarm the bomb.
The missing feature is security between endpoints. You cannot get there by
adding AAA, admin servers, and yet more proxies. That is like trying to
prevent your car from being stolen by loading it up with several tons of
steel. Why not just lock the door? Object based security techniques ought
to do the job.