Capability security for transparent distributed object systems

• US 5,781,633 A
• Filed: 07/01/1996
• Issued: 07/14/1998
• Est. Priority Date: 07/01/1996
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Miller, Mark S., Tribble, E. Dean, Hibbert, Christopher T., Hill, Eric C., Hardy, Norman
• Primary Examiner(s): Barron, Jr., Gilberto
• Application Number:
  US08/671,307
• Time in Patent Office: 743 Days
• Field of Search: 380/3, 380/4, 380/25, 380/30, 395/187.01, 395/200.55, 395/683, 395/684, 395/186, 395/200.31
• US Class Current: 713/167
• CPC Class Codes: G06F 9/468 Specific access rights for resources, e.g. using capability register

Abstract

A system providing capability security for distributed object systems is disclosed. The basic tenet of capability security is that the right to do something to an object (e.g., invoke a particular object'"'"'s methods) is represented solely by the holding of a reference to that object. In each of the preferred embodiments described herein, an object is presumed to hold legitimately a reference to a particular object only if the object knows some unpublicized (except under the conditions required by capability security) key associated with the particular object. That is, an object'"'"'s key is required along with the object'"'"'s reference. So that capability security is preserved when object references are passed between objects in different processes, the object references being passed are encrypted upon transmission and then decrypted upon arrival at their intended destination. This cryptography can be performed by objects or processes using a variety of techniques, including Diffie-Helman or public/private key cryptography. The cryptography performed in the various embodiments ensures that only the intended recipient of the message can decode the object reference and that a misbehaving object cannot convince another object that it possesses a capability it does not have. Some of the disclosed embodiments provide capability security for transparent distributed object systems, wherein a pair of matched transports handle and encrypt inter-process communications between objects in their respective processes.

Claims

1. In a distributed object system wherein communications between objects in different processes are rendered transparent through the use of proxy objects and transports, a proxy object resident in a first process being a local representative of a corresponding remote object resident in a second, different process, said proxy object being responsive to messages associated with said remote object, said transports existing in pairs, a first transport of a pair of transports residing in said first process and including a first in-table and a first out-table matched, respectively, to a second out-table and a second in-table in a second transport of said pair of transports resident in said second process, said pair of transports enabling communication between said proxy object and said corresponding remote object by providing corresponding slots in said first and second in- and out-tables, such that a third object in said first process desiring to send a message to said remote object sends said message locally to said proxy object as if said proxy object were said remote object, said proxy object, upon receiving said message, relaying said message to said first transport designating said remote object as recipient using a first index designated for sole use of said proxy object and said remote object, said first transport being configured to relay said message to said in-table of said second transport at said first index, said second transport being configured to relay said message received at said first index to a unique object in said second process associated with said first index, said unique object being said remote object due to correspondence in transport indices of said proxy and remote objects, a capability security system, comprising:

a public and private key associated with each of said processes; and

an agreed key shared by said first and second processes;

said first and second processes being configured to generate cooperatively said agreed key from their own public and private keys according to agreed key encryption techniques;

such that, upon receiving a message from a first object in said first process directed to a second object in said second process identified by a transparent reference, said first transport is configured to encode said message using said agreed key and to transmit said encoded message to a second transport in said second process;

said second transport being configured to decode said encoded message using said agreed key and to direct the decoded message to said second object based on said transparent reference, messages between said first and second processes being encrypted with said agreed key, thereby ensuring secure inter-process message-passing with transparency.

2. The system of claim 1, further comprising:

a registrar in each process;

a secret number table maintained by said registrar for local objects in said process, each entry in said secret number table including;

a unique to said registrar, practically unguessable secret code associated with one of said local objects, and

a strong pointer to said one object, said registrar being configured to respond to messages directed to a local object via said secret code of said local object by looking up said local object using said strong pointer; and

a registrar slot with a predetermined registrar index in said in-tables and out-tables, said registrar slot in said in-table including a pointer to the local registrar in the same process as said in-table so as to allow objects remote from said local registrar to access objects registered with said local registrar by issuing messages to said registrar slot designating secret codes of said objects to be accessed.

3. The system of claim 1, further comprising:

a fourth object resident in said first process;

wherein said message issued by said third object to said proxy object is a language-level message passing an object reference for said fourth object to said remote object;

such that;

upon receiving said language-level message, said proxy being configured to pass said language-level message to said first transport designating said remote object as recipient by using said first index, said first transport manager being configured to issue a corresponding, encrypted network message directed to said first index of said in-table of said second transport, said encrypted message identifying a type of proxy to be created, said type being a fourth object proxy, and a designated index in said out-table of said second process to be associated with said proxy to be created, said designated index corresponding to a second index reserved in said first intable for said fourth object; and

upon receiving said message, said second transport being configured to decode said encrypted message, create said fourth object proxy, reserve said second index in said out-table of said second transport and link said fourth object proxy to said second index of said second out-table so that said fourth object and said fourth object proxy can communicate between said first and second processes using said second index.

4. The system of claim 1, further comprising:

a fourth object resident in said second process;

a fourth object proxy in said first process that is a proxy of said fourth object; and

a second index associated solely with said fourth objects in said first and second in-tables and out-tables;

wherein said third object is configured to issue a message directing said remote object to perform an action on said fourth object by relaying said message though said proxy object, said message comprising (1) a message name indicating said action to be performed and (2) an object reference identifying a target of said action, said object reference comprising said second index;

such that;

upon receiving said message, said proxy object being configured to relay said message to said first transport designating said remote object as recipient by using said first index, said message being securely transmitted between said first and second processes by said first and second transports and then passed through said in-table of said second transport to said remote object; and

upon receiving said message comprising said object reference, said remote object being configured to perform said action directly on said fourth object.

5. The system of claim 2, further comprising:

a third process;

a third registrar resident in said third process;

a fourth object resident in said third process having an associated fourth secret code maintained by said third registrar;

wherein said message issued by said third object to said proxy object is a language-level message passing an object reference for said fourth object to said remote object;

said proxy object being configured, upon receiving said language-level message, to pass said object-reference message to said out-table of said first transport at said first index;

said first transport being configured, upon receiving said object-reference message to obtain said fourth secret code and issue a third-party message to said second transport, said third-party message including;

a submessage name identifying a type of proxy to be created, said type being said fourth object proxy;

location information designating global address of said third process;

the public key associated with said third process; and

said fourth secret code;

said second transport being configured, upon receiving said third party message, to;

when a pair of transports does not exist to support communications between said second and third processes, allocate a new pair of transports comprising a fifth and sixth transport resident, respectively, in said second and third processes;

allocate a third registrar proxy object in said second process linked to said third registrar object when one does not exist;

issue a lookup message to said third process registrar proxy object, said lookup message designating said fourth secret code, said third process registrar proxy object being configured to relay said lookup message to said third process registrar object via said predetermined registrar index in said out- and in-tables of said fifth and sixth transports;

said third registrar being configured, upon receiving said lookup message, to return a message to said fifth transport directing said fifth transport to create a new fourth proxy in said second process linked to said fourth object via a designated slot index in said out- and in-tables of said fifth and sixth transports.

6. The system of claim 5, further comprising:

a third registrar proxy resident in said first process linked to said third registrar;

a fourth object proxy resident in said first process linked to said fourth object;

wherein said transports include a remember method, the purpose of which to obtain said secret codes;

said first transport being configured, upon receiving said language level message, to issue a remember message to said third registrar proxy requesting a fourth secret code associated with said fourth object;

said third registrar proxy being configured, upon receiving said remember message, to relay said remember message to said third registrar via said predetermined registrar index in said third and fourth transports; and

said registrar being configured, upon receiving said remember message, to return said fourth object'"'"'s secret code to said first transport manager via same pair of transports.

19. The system of claim 1, wherein said agreed key encryption techniques comprise Diffie-Helman key-exchange cryptography.

7. In a distributed object system wherein communications between objects in different processes are rendered transparent through the use of proxy objects and transports, said transports existing in pairs, a first transport of a pair of transports residing in a first process and including a first in-table and a first out-table matched, respectively, to a second out-table and a second in-table in a second transport of said pair of transports resident in a second process, said pair of transports enabling communication between a proxy object in said first process and its corresponding remote object in said second process by providing corresponding slots in said first and second in-and out-tables, a capability security method, comprising the steps of:

generating a public and private key for each of said processes;

generating an agreed key for said first and second processes according to key-exchange principles based on said public and private keys of said first and second processes;

said first transport, upon receiving a message from said proxy object directed to a recipient associated with a particular index in said first out-table, encrypting said message using said agreed key and transmitting the encrypted message to said second transport at said particular index of said second in-table;

said second transport, upon receiving said encrypted message, decrypting said encrypted message using said agreed key and directing the decoded message to said remote object associated in second in-table with said particular index.

8. The method of claim 7, further comprising the steps of:

a third object in said first process issuing a language-level message passing an object reference for a fourth object in said first process to said remote object;

said proxy responding to said language-level message and issuing said object reference message to said remote object by designating as recipient'"'"'s index said particular index;

said first transport, upon receiving said object reference message;

when a fourth index is not yet available for said fourth object in said first in-table, reserving said fourth index, said fourth index serving as said object reference for said fourth object as between said first and second processes; and

issuing a corresponding, encrypted network message directed to said first index of said in-table of said second transport, said encrypted message identifying a type of proxy to be created, said type being a fourth object proxy, and a designated index in said out-table of said second process to be associated with said proxy to be created, said designated index corresponding to said fourth index; and

said second transport, upon receiving said encrypted network message;

creating said fourth object proxy in said second process;

reserving said second index in said second out-table and linking said fourth object proxy to said second index of said second out-table so that said fourth object and said fourth object proxy can communicate between said first and second processes using said second index; and

passing a language-level object reference message including said fourth object'"'"'s object reference to said remote object, thereby conferring on said remote object the capability to access said fourth object in said first process via said fourth object proxy.

9. The method of claim 7, further comprising the steps of:

a third object in said first process issuing a language-level object reference message passing an object reference for a fourth object in a third process to said remote object;

said proxy responding to said object reference message and issuing said object reference message to said first-out table at said particular index;

said first transport, upon receiving said object-reference message;

obtaining a fourth secret code maintained for said fourth object by a third registrar in said third process, and

issuing a third-party message to said second transport, said third-party message including;

a submessage name identifying a type of proxy to be created, said type being said fourth object proxy,

location information designating global address of said third process,

the public key associated with said third process, and

said fourth secret code;

said second transport, upon receiving said third party message;

when a pair of transports does not exist to support communications between said second and third processes, allocating a new pair of transports comprising a fifth and sixth transport resident, respectively, in said second and third processes,

allocating a third registrar proxy object in said second process linked to said third registrar object when one does not exist, and

issuing a lookup message to said third process registrar proxy object, said lookup message designating said fourth secret code, said third process registrar proxy object being configured to relay said lookup message to said third process registrar object via said predetermined registrar index in said out- and in-tables of said fifth and sixth transports; and

said third registrar, upon receiving said lookup message, returning a message to said fifth transport directing said fifth transport to create a new fourth proxy in said second process linked to said fourth object via a designated slot index in said out- and in-tables of said fifth and sixth transports.

10. The method of claim 9, wherein said step of obtaining said fourth secret code comprises:

said first transport, upon receiving said language level message, issuing a remember message to a third registrar proxy requesting said fourth secret code associated with said fourth object;

said third registrar proxy, upon receiving said remember message, relaying said remember message to said third registrar via said predetermined registrar index in said third transport and a fourth transport in said third process linked to said third transport; and

said registrar, upon receiving said remember message, returning said fourth object'"'"'s secret code to said first transport manager via same pair of transports.

20. The system of claim 7, wherein said agreed key encryption principles comprise Diffie-Helman key-exchange cryptography.

11. In a transparent, distributed object system, a capability security system, comprising:

a public and private key associated with each of a subset of processes composing said transparent, distributed object system; and

an agreed key shared by a pair of said subset of processes hosting objects that are communicating via transports and proxy objects provided by said pair, said pair including first and second processes and said transports including first and second transports;

said first and second processes being configured to generate cooperatively said agreed key from their own public and private keys according to agreed key encryption techniques;

such that, upon receiving a message from a first object in said first process directed to a second object in said second process identified by a transparent reference, said first transport is configured to encode said message using said agreed key and to transmit said encoded message to a second transport in said second process;

said second transport being configured to decode said encoded message using said agreed key and to direct the decoded message to said second object based on said transparent reference, messages between said first and second processes being encrypted with said agreed key, thereby ensuring secure inter-process message-passing with transparency.

12. The system of claim 11, further comprising:

a registrar in each process;

a secret number table maintained by said registrar for local objects in said process, each entry in said secret number table including;

a unique to said registrar, practically unguessable secret code associated with one of said local objects, and

a strong pointer to said one object, said registrar being configured to respond to messages directed to a local object via said secret code of said local object by looking up said local object using said strong pointer; and

a registrar slot with a predetermined registrar index in in-tables and out-tables, said registrar slot in said in-table including a pointer to the local registrar in the same process as said in-table so as to allow objects remote from said local registrar to access objects registered with said local registrar by issuing messages via said transports designating as the message destination said predetermined registrar index and including secret codes of said objects to be accessed.

13. The system of claim 11, further comprising:

a third object in said first process;

a remote object in said second process;

a proxy object in said first process associated with said remote object via a common first index in said first transport'"'"'s out-table and said second transport'"'"'s in-table, said third object being configured to send a message to said remote object via said proxy object;

a fourth object resident in said first process;

wherein said message issued by said third object to said proxy object is a language-level message passing an object reference for said fourth object to said remote object;

said proxy object being configured upon receiving said language-level message to pass said language-level message to said first transport designating said remote object as recipient by using said first index, said first transport manager being configured to issue a corresponding, encrypted network message directed to said first index of said in-table of said second transport, said encrypted message identifying a type of proxy to be created, said type being a fourth object proxy and a designated index in said out-table of said second process to be associated with said proxy to be created, said designated index corresponding to a second index reserved in said first in-table for said fourth object; and

said second transport being configured upon receiving said message to decrypt said message, create said fourth object proxy, reserve said second index in said out-table of said second transport, link said fourth object proxy to said second index of said second out-table so that said fourth object and said fourth object proxy can communicate between said first and second processes using said second index and pass said decrypted message to said remote object.

14. The system of claim 11, further comprising:

a third object in said first process;

a remote object in said second process;

a proxy object in said first process associated with said remote object via a common first index in said first transport'"'"'s out-table and said second transport'"'"'s in-table, said third object being configured to send a message to said remote object via said proxy object;

a fourth object resident in said second process;

a fourth object proxy in said first process that is a proxy of said fourth object; and

a second index associated solely with said fourth objects in said first and second in-tables and out-tables;

wherein said third object is configured to issue a message directing said remote object to perform an action on said fourth object by relaying said message though said proxy object, said message comprising (1) a message name indicating said action to be performed and (2) an object reference identifying a target of said action, said object reference comprising said second index;

such that;

upon receiving said message, said proxy object is configured to relay said message to said first transport designating said remote object as recipient using said first index, said message being securely transmitted between said first and second processes by said first and second transports and then passed through said in-table of said second transport via said first index to said remote object; and

upon receiving said message including said object reference, said remote object is configured to perform said action directly on said fourth object.

15. The system of claim 12, further comprising:

a third object in said first process;

a remote object in said second process;

a proxy object in said first process associated with said remote object via a common first index in said first transport'"'"'s out-table and said second transport'"'"'s in-table, said third object being configured to send a message to said remote object via said proxy object;

a third process;

a third registrar resident in said third process;

a fourth object resident in said third process having an associated fourth secret code maintained by said third registrar;

wherein said message issued by said third object to said proxy object is a language-level message passing an object reference for said fourth object to said remote object;

said proxy object being configured, upon receiving said language-level message, to pass said language-level message to said first transport designating said remote object as recipient by using said first index;

said first transport being configured, upon receiving said language-level message to obtain said fourth secret code and issue a third-party message to said second transport, said third-party message including;

a submessage name identifying a type of proxy to be created, said type being said fourth object proxy;

location information designating global address of said third process;

the public key associated with said third process; and

said fourth secret code;

said second transport being configured, upon receiving said third party message, to;

when a pair of transports does not exist to support communications between said second and third processes, allocate a new pair of transports comprising a fifth and sixth transport resident, respectively, in said second and third processes;

allocate a third registrar proxy object in said second process linked to said third registrar object when one does not exist;

issue a lookup message to said third process registrar proxy object, said lookup message designating said fourth secret code, said third process registrar proxy object being configured to relay said lookup message to said third process registrar object via said predetermined registrar index in said out- and in-tables of said fifth and sixth transports;

said third registrar being configured, upon receiving said lookup message, to return a message to said fifth transport directing said fifth transport to create a new fourth proxy in said second process linked to said fourth object via a designated slot index in said out- and in-tables of said fifth and sixth transports.

16. The system of claim 15, further comprising:

a third registrar proxy resident in said first process linked to said third registrar;

a fourth object proxy resident in said first process linked to said fourth object;

wherein said transports include a remember method, the purpose of which is to obtain said secret codes;

said first transport being configured, upon receiving said language level message, to issue a remember message to said third registrar proxy requesting a fourth secret code associated with said fourth object;

said third registrar proxy being configured, upon receiving said remember message, to relay said remember message to said third registrar via said predetermined registrar index in said third and fourth transports; and

said registrar being configured, upon receiving said remember message, to return said fourth object'"'"'s secret code to said first transport manager via same pair of transports.

17. The system of claim 11, wherein said transparent reference comprises a first out-table index in a first out-table in said first transport and a different second in-table index in a second in-table in said second transport, said first transport manager being configured to derive said second in-table index from said first out-table index, which is provided by said first object as destination of said message.

18. The system of claim 11, wherein said transparent reference comprises a first out-table index in a first out-table in said first transport and a different second in-table index in a second in-table in said second transport, said first object providing destination of said message as an index pair including said first out-table index and said second in-table index, said first transport manager being configured to deliver said message to a destination object designated by said second in-table index.

21. The system of claim 11, wherein said agreed key encryption techniques comprise Diffie-Helman key-exchange cryptography.