Robert Wahbe, Steven Lucco, Thomas E. Anderson, and Susan L. Graham. E#cient software-based fault isolation. In Proceedings of the 14th ACM Symposium on Operating Systems Principles (SOSP '93), pages 203--216, New York, 1993. ACM Press. ISBN 0-89791-632-8. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents
Automated Techniques for Provably Safe Mobile Code - Colby, Crary, Harper, Lee.. (2001) (2 citations) (Correct)
....problem of safe component integration: 1) Run time checking. Untrusted components are monitored at execution time to ensure that their interactions with other components are strictly limited. Typical techniques include isolation in separate hardware address spaces and software fault isolation [1]. These methods impose serious performance penalties in the interest of safety. Moreover, there is often a large semantic gap between the low level properties that are guaranteed by checking (e.g. address space isolation) and the high level properties that are required (e.g. black box ....
R. Wahbe, S. Lucco, T. Anderson, S. Graham, E#cient software-based fault isolation, in: 14th ACM Symposium on Operating System Principles, 1993, pp. 203--216.
Sharing in Typed Module Assembly Language - Duggan (2000) (14 citations) (Correct)
....[36] In the OS research community, investigation of alternatives has been motivated by the demands of modular micro kernel operating systems, where OS modules outside the kernel might not be trusted. Software fault isolation (where the loader inserts software sandboxing checks into machine code [35]) and the SPIN project (where type safe OS modules are compiled by a trusted compiler R. Harper (Ed. TIC 2000, LNCS 2071, pp. 85 116, 2001. c Springer Verlag Berlin Heidelberg 2001 [5] are examples of approaches to providing protection in software rather than hardware. Sandboxing in Java ....
Robert Wahbe, Steven Lucco, Thomas E.Anderson, and Susan L.Graham. E#cient software-based fault isolation. In Symposium on Operating Systems Principles, pages 203--216. ACM Press, 1993.
Resource Control of Untrusted Code in an Open Network Environment - Menage (2003) (2 citations) (Correct)
....to be written in a safe language has the disadvantage of reducing the flexibility available to remote users. An alternative approach taken by some researchers has been to develop ways to permit arbitrary machine code or assembly language to be executed safely. Software Fault Isolation (SFI) Wahbe93] runs each untrusted code module in a separate fault domain. A fault domain is a region of memory associated with the untrusted module, within which all loads and stores and most jumps are unrestricted. Code to be run is required to execute special bounds checking code before any memory ....
....provided by the node is su#ciently encompassing, most execution time will be spent in these system libraries, and the e#ciency of the user supplied code will be less relevant. Three other possibilities for supplying safe code were considered but rejected: 1. Software Fault Isolation (SFI) Wahbe93] would provide a guarantee that the application was not able to access objects to which it did not have any access; however, it would be unable to guarantee that the application respected the type safety of objects within its heap. This would result in Rcane being unable to store any data within ....
[Article contains additional citation context not shown here]
Robert Wahbe, Steven Lucco, Thomas E. Anderson, and Susan L. Graham. E#cient Software-Based Fault Isolation. In Proceedings of the 14th ACM Symposium on Operating Systems Principles, pages 203--216, 1993.
Bridging the Gap between TCPA/Palladium and Personal Security - Sadeghi, Stüble (2003) (Correct)
....between local process identifiers and authentication codes. An Application Manager controls the applications to be installed and enforces a user defined security policy. Possible instantiations would be the use of code signing, source code analysis, object analysis, or proof carrying code [27, 26, 32, 21]. The application manager uses the cryptographic features of the TCPA Pd hardware to be able to decrypt DRM applications and then generates unique identifier for applications (e.g. an authentication code for the TCPA Pd hardware and a unique identifier for the authentication by users) ....
R. Wahbe, S. Lucco, T. E. Anderson, and S. L. Graham. E#cient software-based fault isolation. ACM SIGOPS Operating Systems Review, 27(5):203--216, December 1993.
Isolation, Resource Management and Sharing in the Kaffeos Java.. - Back (2002) (Correct)
....to the heap. We use write barriers [87] for that purpose. A write barrier is a check that happens on every write of an object reference into the heap. As we show in Section 5.1, the cost of using write barriers, although non negligible, is reasonable. Unlike for 32 software fault isolation schemes [83], we do not need to instrument every store machine instruction in Java, write barriers need to be inserted only for certain Java bytecode instructions. These instructions are PUTFIELD, PUTSTATIC, AASTORE, and any assignment within the VM or in native libraries that creates a connection between ....
Wahbe, R., Lucco, S., Anderson, T., and Graham, S. E#cient software-based fault isolation. In Proceedings of the 14th Symposium on Operating Systems Principles (Asheville, NC, December 1993), pp. 203--216.
IRM Enforcement of Java Stack Inspection - Erlingsson, Schneider (2000) (41 citations) (Correct)
....updates to be associated with any application event. This degree of flexibility can be only approximated by wrapping security enforcement code around an interface, as done by Naccio [8] for method calls) and Generic Software Wrappers [9] for system calls) Software based fault isolation (SFI) [17] enforces a memory protection policy by object code editing, and recent work on distributed virtual machines also is concerned with enforcing security policies by code rewriting [16] Clearly, the set of enforceable security policies is restricted if, as in this related work, only some not ....
Wahbe, R., S. Lucco, T.E. Anderson, and S.L. Graham. E#cient Software-Based Fault Isolation. Operating System Review, 27(5), ACM Press, 1993.
Interfacing Compilers, Proof Checkers, and Proofs for Foundational.. - Wu (2005) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas E. Anderson, and Susan L. Graham. E#cient software-based fault isolation. In Proceedings of the 14th ACM Symposium on Operating Systems Principles (SOSP '93), pages 203--216, New York, 1993. ACM Press. ISBN 0-89791-632-8.
GIVS: Integrity Validation for Grid Security - And (Correct)
No context found.
Wahbe, R., Lucco, S., Anderson, T.E., Graham, S.L.: E#cient software-based fault isolation. In: Proc. of the 14th ACM Symp. on O.S. princ., ACM Press (1993) 203--216
Secure Untrusted Binaries Provably! - Simon Winwood And (Correct)
No context found.
Wahbe, R., Lucco, S., Anderson, T.E., Graham, S.L.: E cient software-based fault isolation. ACM SIGOPS Operating Systems Review 27 (1993) 203216
Proof Linking: A Modular Verification Architecture for Mobile Code .. - Fong (2004) (2 citations) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas E. Anderson, and Susan L. Graham. E#- cient software-based fault isolation. In Proceedings of the 14th ACM Symposium on Operating Systems Principles, pages 203--216, Asheville, North Carolina, December 1993.
Code Inection in C and CPP: A Survey of Vulnerabilities.. - Younan, Joosen, Piessens (2004) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas E. Anderson, and Susan L. Graham. E#cient Software-Based Fault Isolation. In Proceedings of the 14th ACM Symposium on Operating System Principles, pages 203--216, Asheville, North Carolina, U.S.A., December 1993. ACM. (Cited on pages 33, 34 and 63.)
Slinky: Static Linking Reloaded - Christian Collberg John (2004) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas E. Anderson, and Susan L. Graham. E#cient software-based fault isolation. ACM SIGOPS Operating Systems Review, 27(5):203--216, December 1993.
Typed Memory Management in a Calculus of Capabilities - Walker, Crary, Morrisett (2000) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas Anderson, and Susan Graham. E#cient software-based fault isolation. In Fourteenth ACM Symposium on Operating Systems Principles, pages 203--216, Asheville, December 1993.
A Type System for Expressive Security Policies - Walker (1999) (28 citations) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas Anderson, and Susan Graham. E#cient software-based fault isolation. In Fourteenth ACM Symposium on Operating Systems Principles, pages 203--216, Asheville, December 1993.
Project Description - We Propose To (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas Anderson, and Susan Graham. E#cient software-based fault isolation. In Fourteenth ACM Symposium on Operating Systems Principles, pages 203-- 216, Asheville, December 1993.
Protection in the Think exokernel - Christophe Rippert Jean-Bernard (Correct)
No context found.
Robert Wahbe and Steven Lucco and Thomas E. Anderson and Susan L. Graham. E#cient Software-Based Fault Isolation. ACM Special Interest Group on OPerating Systems, 1993.
Transforming Policies into Mechanisms with Infokernel - Arpaci-Dusseau.. (2003) (3 citations) (Correct)
No context found.
R. Wahbe, S. Lucco, T. Anderson, and S. Graham. E#cient Software-Based Fault Isolation. In Proceedings of the 14th ACM Symposium on Operating Systems Principles (SOSP '93), pages 203--216, Asheville, North Carolina, December 1993.
Formalizing Java-MaC - Sammapun, Sharykin, DeLap, Kim.. (2003) (Correct)
No context found.
R. Wahbe, S. Lucco, T. Anderson, and S. Graham. E#cient software-based fault isolation. In Proc. 14th ACM Symp. on Operating System Principles (SOSP), pages 203--216. ACM Press, December 1993.
Improving the Reliability of Commodity Operating Systems - Swift, Bershad, Levy (2003) (12 citations) (Correct)
No context found.
R. Wahbe, S. Lucco, T. E. Anderson, and S. L. Graham. E#cient software-based fault isolation. In Systems Principles, pages 203--216, Dec. 1993.
Safe Programming at the C Level of Abstraction - Grossman (2003) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas Anderson, and Susan Graham. E#- cient software-based fault isolation. ACM SIGOPS Operating Systems Review, 7(5):203--216, December 1993.
Computability Classes for Enforcement Mechanisms - Hamlen, Morrisett, Schneider (2003) (8 citations) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas E. Anderson, and Susan L. Graham. E#cient softwarebased fault isolation. In Proceedings of the 14th ACM Symposium on Operating Systems Principles, pages 203--216, December 1993.
HOKES/POKES: Light-weight resource sharing - Bos, Samwel (Correct)
No context found.
R. Wahbe, S. Lucco, T.E. Anderson, and S.L. Graham. E#cient softwarebased fault-isolation. In SOSP'03, pages 203--216, December 1993.
Protection in Flexible Operating System Architectures - Rippert (Correct)
No context found.
R. Wahbe, S. Lucco, T. E. Anderson, and S. L. Graham. E#cient Software-Based Fault Isolation. ACM SIGOPS Operating Systems Review, 27(5):203--216, 1993.
A Taxonomy of Computer Worms - Weaver, Paxson, Staniford, Cunningham (2003) (19 citations) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas E. Anderson, and Susan L. Graham. E#cient Software-Based Fault Isolation. ACM SIGOPS Operating Systems Review, 27(5):203--216, December 1993.
Computability Classes for Enforcement Mechanisms - Hamlen, Morrisett, Schneider (2003) (8 citations) (Correct)
No context found.
Robert Wahbe, Steven Lucco, Thomas E. Anderson, and Susan L. Graham. E#cient softwarebased fault isolation. In Proceedings of the 14th ACM Symposium on Operating Systems Principles, pages 203--216, December 1993.
First 50 documents
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