D. England, Capability, Concept, Mechanism and Structure in System 250, RAIROInformatique (AFCET), Vol 9, September 1975. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Non-Functional Capability-Based Access Control in the Java.. - Hagimont, De Palma (Correct)
....code is embedded in the caller and callee objects (however we have to pass new parameters to implement the capability transfer) 6 Related Work Early attempts to manage protection by means of capabilities were based on specific hardware. Several capability based hardware addressing systems [5][12] were built for the management of protected shared objects. These machine and system architectures were very popular in the 70s, but the standardization of the hardware and the widespread use of Unix systems stopped the trend towards capability based architectures. In a second step, software ....
D. England, Capability, Concept, Mechanism and Structure in System 250, RAIROInformatique (AFCET), Vol 9, September 1975.
Hidden Software Capabilities - Hagimont, Mossière, de Pina.. (1996) (12 citations) (Correct)
....the principles of both implementations, and we then present the requirements we place on our capability based protection model. Hardware Capabilities Early attempts to manage protection bymeans of capabilities were based on specific hardware. Several capabilitybased hardware addressing systems [4][13] were built for the management of protected shared objects. These systems are characterized by the way objects are addressed at run time. The machine has a set of capability registers. Operands in memory are addressed in a machine instruction through a capability register. Therefore, ....
D. M. England. Capability, concept, mechanism and structure in system 250. RAIRO-Informatique (AFCET), (9):47-- 62, September 1975.
Access Control in a Distributed Shared Memory - Jensen, Hagimont (Correct)
....thereby limiting application evolution and software reuse. To avoid these problems, we want to separate capability management from the application code. The proposed mechanism answers this requirement. The following assumes basic knowledge of the principles of capabilitybased protection [Eng75, Lev84] A full description of our protection model is given in section 3. 1.2 Hidden Software Capabilities Principle The protection model we propose is based on Hidden Software Capabilities [HMdPS96] a protection scheme designed by our group. The model is based on the concepts of ....
D. M. England. Capability, concept, mechanism and structure in system 250. RAIROInformatique (AFCET), 9:4762, September 1975.
Hidden Software Capabilities - Hagimont, de Pina, Saunier (1996) (12 citations) (Correct)
....principles of both implementations, and we then present the requirements we place on our capability based protection model. Hardware Capabilities Early attempts to manage protection by means of capabilities were based on specific hardware. Several capability based hardware addressing systems [England 75] Wilkes 79] were built for the management of protected shared objects. These systems are characterized by the way objects are addressed at run time. The machine has a set of capability registers. Operands in memory are addressed in a machine instruction through a capability register. Therefore, ....
D. M. England. Capability, Concept, Mechanism and Structure in System 250, RAIROInformatique (AFCET), Vol 9, pp. 47-62, September 1975.
A Protection Scheme for a CORBA Environment - Hagimont, Huet, Mossière (1997) (1 citation) (Correct)
No context found.
D. M. England. Capability Concept, Mechanism and Structure in System 250, RAIROInformatique (AFCET), Vol 9, pp. 47-62, September 1975. 17
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC