ACM Home Page
Please provide us with feedback. Feedback
Secure calling contexts for stack inspection
Full text pdf formatPdf (271 KB)
Source International Conference on Principles and Practice of Declarative Programming archive
Proceedings of the 4th ACM SIGPLAN international conference on Principles and practice of declarative programming table of contents
Pittsburgh, PA, USA
Pages: 76 - 87  
Year of Publication: 2002
ISBN:1-58113-528-9
Authors
Frédéric Besson  IRISA, Campus de Beaulieu, France
Thomas de Grenier de Latour  IRISA, Campus de Beaulieu, France
Thomas Jensen  IRISA, Campus de Beaulieu, France
Sponsor
SIGPLAN: ACM Special Interest Group on Programming Languages
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 3,   Downloads (12 Months): 16,   Citation Count: 6
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/571157.571166
What is a DOI?

ABSTRACT

Stack inspection is a mechanism for programming secure applications by which a method can obtain information from the call stack about the code that (directly or indirectly) invoked it. This mechanism plays a fundamental role in the security architecture of Java and the .NET Common Language Runtime. A central problem with stack inspection is to determine to what extent the <i>local</i> checks inserted into the code are sufficient to guarantee that a <i>global</i> security property is enforced. In this paper, we present a technique for inferring a <i>secure calling context</i> for a method. By a secure calling context we mean a pre-condition on the call stack sufficient for guaranteeing that execution of the method will not violate a given global property. This is particularly useful for annotating library code in order to avoid having to re-analyse libraries for every new application. The technique is a constraint based static program analysis implemented via fixed point iteration over an abstract domain of linear temporal logic properties.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
 
3
M. Bartoletti, P. Degano, and G. Ferrari. Static analysis for stack inspection. In Proc. of Int. workshop on Concurrency and Coordination (ConCoord 2001), Electronic Notes in Theoretical Computer Science vol. 54. Elsevier, 2001.
 
4
5
6
7
8
 
9
10
11
 
12
L. Gong. Going beyond the sandbox: An overview of the new security architecture in the Java development kit 1.2. In Proc. of USENIX Symposium on Internet Technologies and Systems, Dec. 1997.
13
 
14
T. Jensen, D. Le Métayer, and T. Thorn. Verification of control flow based security properties. In Proc. of the 20th IEEE Symp. on Security and Privacy, pages 89--103. New York: IEEE Computer Society, 1999.
 
15
Microsoft Corp. Secure Coding Guidelines for the .NET Framework. Microsoft Corp., 2002.
 
16
 
17
 
18
 
19
20
21
 
22
M. Y. Vardi. An Automata-Theoretic Approach to Linear Temporal Logic, volume 1043 of Lecture Notes in Computer Science, pages 238--266. Springer-Verlag Inc., New York, NY, USA, 1996.
 
23
 
24
D. S. Wallach and E. W. Felten. Understanding Java stack inspection. In 1998 IEEE Symposium on Security and Privacy, May 1998.


Collaborative Colleagues:
Frédéric Besson: colleagues
Thomas de Grenier de Latour: colleagues
Thomas Jensen: colleagues

Peer to Peer - Readers of this Article have also read: