Inter-object messaging

Details Inter-object messaging Inter-object messaging

1997-03-31

2004-05-25

Follansbee, John (Department: 2126)

Electrical computers and digital processing systems: multicomput

Computer-to-computer data routing

Least weight routing

C713S167000

Reexamination Certificate

active

06742050

ABSTRACT:

FIELD OF THE INVENTION
The present invention relates to object oriented programming. More specifically, the present invention relates to a secure method of communication with untrusted JAVA™ objects.
BACKGROUND OF THE INVENTION
JAVA™ is a portable language that generates intermediate code that can be downloaded and run on a machine with a JAVA™ interpreter. The portability of JAVA™ applets allows processing to be off-loaded to a local system that has the potential capability of performing the processing at a faster rate than the source of the applet.
Because applets are designed to be loaded from a remote site and then executed locally, security is an important issue. In order to prevent untrusted code from damaging the local system, web browsers with JAVA™ interpreters often implement safeguards that restrict what applets can do. Some safeguards include, preventing applets from running any local executable program and preventing applets from communicating with any host other than their originating host. Other safeguards include preventing applets from reading or writing the local computer's file system and preventing applets from finding information about the local client system other than the JAVA™ version used, the name and version of the operating system, the characters used to separate files, paths, and lines.
The safeguards implemented by web browsers, however, are ineffective in providing a secure method of communication between untrusted objects from the untrusted code and objects in the local system. The safeguards implemented by current web browsers allow trusted objects to communicate with other trusted objects in the local system by making direct method calls directly on the objects in the local system. Direct method calls are messages from one object to another that request the receiving object to carry out one of its methods. A direct method call typically consists of three parts: a reference to the receiver object, the name of the method in the receiver object to be executed, and any parameters that the method may require to fulfill its charge. If untrusted objects were allowed to make direct method calls to other objects in the local system, untrusted objects could potentially do damage to a file system, a network, invoke methods in an inappropriate manner, or negatively affect other parts of the local system.
Thus, a method for inter-object communication among objects that minimizes the dangers associated with allowing untrusted objects to make direct method calls is desired.
SUMMARY
A method of communication between a first object and a second object is disclosed. A first direct method call is made on an intermediary object from the first object. The first direct method call contains information regarding a location in memory of the intermediary object and a name of the method to be called on the second object. The name of the method to be called on the second object is delivered from the intermediary object to a message queue object. The name of the method to be called on the second object is accessed from the message queue object by the second object.
A method for requesting a channel of communication with a receiver object via a trusted intermediary is disclosed. A first direct method call is made to a session object to request a channel with the receiver object. A location in memory of a channel object is received from the session object on behalf of the receiver object.
A method of allocating a channel of communication is disclosed. A direct method call is received from a session object on behalf of a sender object requesting a channel of communication. The direct method call contains an object identifier (ID) of the sender object. A degree of access to grant the sender object is determined. A channel object with the degree of access appropriate for the sender object is created. A location in memory of the channel object is returned to the session object.
A method for arbitrating a channel of communication between a first object and a second object is disclosed. A first direct method call is received from the first object requesting a channel of communication with the second object. The first direct method call contains an object identifier (ID) of the first object and the second object. A second direct method call is made to the second object requesting the channel of communication on behalf of the first object. A location in memory of a channel object is received from the second object. The location in memory of the channel object is sent to the first object.


REFERENCES:
patent: 5136716 (1992-08-01), Harvey et al.
patent: 5173939 (1992-12-01), Abadi et al.
patent: 5235642 (1993-08-01), Wobber et al.
patent: 5315657 (1994-05-01), Abadi et al.
patent: 5379426 (1995-01-01), Foss et al.
patent: 5396630 (1995-03-01), Banda et al.
patent: 5414852 (1995-05-01), Kramer et al.
patent: 5450593 (1995-09-01), Howell et al.
patent: 5485617 (1996-01-01), Stutz et al.
patent: 5539909 (1996-07-01), Tanaka et al.
patent: 5551035 (1996-08-01), Arnold et al.
patent: 5742848 (1998-04-01), Burgess
patent: 5751962 (1998-05-01), Fanshier et al.
patent: 5758186 (1998-05-01), Hamilton et al.
patent: 5761421 (1998-06-01), van Hoff et al.
patent: 5778222 (1998-07-01), Herrick et al.
patent: 5784560 (1998-07-01), Kingdon et al.
patent: 5848234 (1998-12-01), Chernick et al.
patent: 5941945 (1999-08-01), Aditham et al.
patent: 6049838 (2000-04-01), Miller et al.
patent: 6192405 (2001-02-01), Bunnell
patent: 6192419 (2001-02-01), Aditham et al.
patent: 6278532 (2001-08-01), Heimendinger et al.
IBM Corp. 1994 . “MQSeries Distributed Queue Management Guide”.*
IBM Corp. 1993. “MQSeries Application Programming Guide”.*
Girdley, Michael et al. “Web Programming with Java”. Jul. 1996.*
Erdos, Marlena et al. “Security Reference Model for the Java Developer's Kit 1.0.2”. Nov. 13, 1996.*
Omg. “CORBA Security Draft”. Sep. 1995.*
Internet. “JAVA Security”. “Using the Security Manager”, p. 1-19.*
Yialelis, Nicholas et al. “A Security Framework Supporting Domain Based Access Control in Distributed Systems”. Sep. 15, 1995.*
Lupu, Emil C. et al. “A Policy Based Role Framework for Access Control”. ACM. Dec. 1995.*
Yialelis, Nicholas et al. “An Authentication Service Supporting Domain Based Access Control Policies.” Sep. 15, 1995.*
Key Logic. “Introduction to KeySAFE” Mar. 1989.*
van Doorn, Leedert et al. “Secure Network Objects.” 1996.*
Dean, Drew. “Java Security: From HotJava to Netscape and Beyond.” IEEE. May 1996.*
Lampson, Butler W. “Protection.” ACM. Jan. 1974.*
Shoffner, Michael et al. “Java and Web-Executable Object Security.” Nov. 1996.*
Buschmann et al. “Pattern-Oriented Software Architecture, A System of Patterns”. Aug. 1996, p. 323-337.*
Christian et al., Designing Object-Oriented Synchronous Groupware with Coast, IPSI- Integrated Publication and Information Systems Institute, GMD-German National Research Center for Information Technology, Dolivostr. 15, D-64293 Darmstadt, Germany (schucki, Kirchner, schimmi, hake) @Darmstadt.gmd.de, 11 Pages.
W. Keith Edwards, Session Management for Collaborative Applications, Graphics, Visualization & Usability Center College of Computing, Georgia Institute of Technology, Atlanta, GA 30332-0280, keith.Edwards@gvu.gatech.edu. 8 Pages.
Generic and Composable Latecomer Accommodation Service for Centralized Shared Systems, Goopeel Chung, Prasun Dewan & Sadagopan Rajaram, Department of Computer Science, University of North Carolina at Chapel Hill, NC 27599-3175 (chungg.dewan.rajaram)@cs.unc.edu., 19 Pages.
The Web Meets MOOS, IRC and the MBONE, Nathan Mates, Mika Nyström, Eve Schooler. 13 Pages, http://www.cs.caltech.edu/—schooler/overview.
U.S. patent application Ser. No. 09/689,027, filed Oct. 11, 2000.
U.S. patent application Ser. No. 08/831,996, filed Apr. 1, 1997.

Affiliated with

Also associated with

Rating

Inter-object messaging does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Inter-object messaging, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Inter-object messaging will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3252938