| PLEX86 | ||
Where should the type information be: in tags and descriptors 416Dan, Thanks for the Mondrian reference. I am not certain what you mean about "flipping protection attributes". I agree that protection ought to be done at an object level and not at a page or word level. buttuming that descriptors are used to describe all storage areas and that operations must utilize descriptors to access any storage and that the descriptors can only be manufactured-changed in properly controlled ways, access control to data is achieved straightforwardly. Different descriptors can cause the referenced data to be treated in different ways (but can complicate the management of the storage area). Similarly if control access is limited to relative jumps within a described code area or to other areas via tagged addresses-descriptors with type code and if operations on these descriptors-tagged addresses can only be done in controlled ways, then much of the work of protection is subsumed by these mechanisms. See Iliffe's books for very detailed examples of all of the above. Where should the type information be: in tags and descriptors 417 Here's an example of what I'm driving at (using Ada syntax, but the same applies to many other languages): type BitMap is... Where should the type information be: in tags and descriptors 419 system's C. That must have been fun as long as you avoided the alligators. Right. :-). That's when my word, thingie, helps... If one organizes one's code and data in the form of objects where each object is responsible for its end and protection, sharing, and synchronization of its data, one does not need protection rings. However one still needs to pbutt (or be able to obtain) authenticated credentials of the user and authenticated data from the environment (perhaps via SAML ) of the subject and make authorization decisions, perhaps by using XACML. Note that in the distributed case, this will be necessary anyway. Simple local R-W sharing of data can be done more straightforwardly. Ed Feustel
----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==---- ---= East-West-Coast Server Farms - Total Privacy via Encryption =--- Where should the type information be: in tags and descriptors 418 Aw heck, I'll byte too :-) The first time I saw this, circa perhaps 1970, it was some CAD data interchange files. All the tables of "things" had current memory address as the identifier for...
|
||||
Where should the type information be: in tags and descriptors 417 Alt Folklore Computers from Newsgroups The #1 Usenet Provider on the Internet
Where should the type information be: in tags and descriptors 415 |
||||