ACM Home Page
Please provide us with feedback. Feedback
Secure mobile agent systems using Java: where are we heading?
Full text PdfPdf (502 KB)
Source Symposium on Applied Computing archive
Proceedings of the 2002 ACM symposium on Applied computing table of contents
Madrid, Spain
SESSION: Agents, interactions, mobility and systems table of contents
Pages: 115 - 119  
Year of Publication: 2002
ISBN:1-58113-445-2
Authors
Walter Binder  CoCo Software Engineering, Margaretenstr. 22/9, 1040 Vienna, Austria
Volker Roth  Fraunhofer IGD, Rundeturmstr. 6, 64283 Darmstadt, Germany
Sponsor
SIGAPP: ACM Special Interest Group on Applied Computing
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 29,   Citation Count: 4
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/508791.508813
What is a DOI?

ABSTRACT

Java is the predominant language for mobile agent systems, both for implementing mobile agent execution environments and for writing mobile agent applications. This is due to inherent support for code mobility by means of dynamic class loading and separable class name spaces, as well as a number of security properties, such as language safety and access control by means of stack introspection. However, serious questions must be raised whether Java is actually up to the task of providing a secure execution environment for mobile agents. At the time of writing, it has neither resource control nor proper application separation. In this article we take an in-depth look at Java as a foundation for secure mobile agent systems.


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
 
4
 
5
 
6
S. Doyon and M. Debbabi. On object initialization in the Java bytecode. Computer Communications, 23(17): 1594-1605, Nov. 2000.
7
 
8
 
9
Java Community Process. JSR 121 --- Application Isolation API Specification. Web pages at http://www.jcp.org/jsr/detail/121.jsp.
 
10


Collaborative Colleagues:
Walter Binder: colleagues
Volker Roth: colleagues