3 citations found. Retrieving documents...
Sirer, E.G., S. McDirmid, and B. Bershad. A Java System Security Architecture. University of Washington Tech. Rep., 1997.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Toward a Provably-Correct Implementation of the JVM.. - Coglio, Goldberg, Qian (1998)   (19 citations)  (Correct)

....consistency for dynamic class loading. He successfully formalized a way to relate bytecode verification and class loading. Saraswat [14] studied static type (un)safety of JAVA in the presence of more than one class loader. We do not consider class loaders in this paper. The Kimera project [15] was quite effective in detecting flaws in commercial bytecode verifiers. Using a comparative testing approach, they wrote a reference bytecode verifier and tested commercial bytecode verifiers against it. A particularly interesting point was that their code is well structured and organized, ....

Sirer, E.G., S. McDirmid, and B. Bershad. A Java System Security Architecture. University of Washington Tech. Rep., 1997.


Constraint-Based Specification and Dataflow Analysis for Java.. - Qian (1998)   (Correct)

....the mechanisms is bytecode verification, which should statically ensure that bytecode will never use data with wrong types in execution. Although the Java industry has been working hard to make their bytecode verifiers secure, several serious flaws have been discovered (and fixed) so far (see e.g. [10,15]) The problem has at least two aspects. The first is to ask whether the specification is adequate to guarantee the security. The official JVM specification (OJVMS) is inadequate, since it is ambiguous and hard to reason about. Therefore, recent research work (e.g. 17,5,13] proposes using formal ....

....and class loading. Since he did not consider subroutines, he did not encounter the problems we discuss in this paper. Saraswat [14] studied static type (un)safety in Java in the presence of more than one class loader. We do not consider class loaders in this paper. The Kimera project [15] was quite effective in detecting flaws in commercial bytecode verifiers. Following the comparative testing approach, they wrote a reference bytecode verifier and tested commercial bytecode verifiers 40 against it. Since it was built by a simple organization of implementations of individual ....

E. Sirer, S. McDirmid, and B. Bershad. A Java system security architecture. http://kimera.cs.washington.edu/, 1997.


A Formal Specification of Java Virtual Machine Instructions for.. - Qian (1998)   (52 citations)  (Correct)

....subroutine. His idea is to use a kind of special types indicating that a certain memory location in a subroutine always has the same content as a memory location at a call to the subroutine. The Kimera project is quite successful in testing some running bytecode verifiers and detecting some flaws [14]. In general, testing is often based on a precise specification. Thus a formal specification may be useful for testing. Dean [3] studied a formal model relating static typing and dynamic linking and proved the safety of dynamic linking with respect to static typing. As mentioned before, our ....

E. Sirer, S. McDirmid, and B. Bershad. A Java system security architecture. http://kimera.cs.washington.edu/, 1997.

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