Sun Microsystems, Inc.

Auspex Systems, Inc.

Oracle America, Inc.

Mitchel B Butler

Joshua Susser

Andy Streich

David R Kandasamy

Andrew L Foss

Michael T Ribble

Dieter Rothmeier

Chintamani M Patwardhan

Gaudencio Ramil

Bradley M Peterson

Andrew Streich

Eduard De Jong

A small footprint device can securely run multiple programs from unrelated vendors by the inclusion of a context barrier isolating the execution of the programs. The context barrier performs security checks to see that principal and object are within the same namespace or memory space and to see that a requested action is appropriate for an object to be operated upon. Each program or set of programs runs in a separate context. Access from one program to another program across the context barrier can be achieved under controlled circumstances by using an entry point object. The entry point object can either perform accesses across the context barrier on behalf of a requesting program or can pass the request to the program to be accessed and switch contexts to the program to be accessed.

Techniques for permitting access across a context barrier on a small footprint device using an entry point object

A small footprint device, such as a smart card, can securely run multiple programs from unrelated vendors by the inclusion of a context barrier isolating the execution of the programs. The context barrier performs security checks to see that principal and object are within the same namespace or memory space and to see that a requested action is appropriate for an object to be operated upon.

Techniques for implementing security on a small footprint device using a context barrier

A small footprint device can securely run multiple programs from unrelated vendors by the inclusion of a context barrier isolating the execution of the programs. The context barrier performs security checks to see that principal and object are within the same namespace or memory space and to see that a requested action is appropriate for an object to be operated upon. Each program or set of programs runs in a separate context. Access from one program to another program across the context barrier can be achieved under controlled circumstances by using a global data structure.

Techniques for permitting access across a context barrier in a small footprint device using global data structures

A small footprint device can securely run multiple programs from unrelated vendors by the inclusion of a context barrier isolating the execution of the programs. The context barrier performs security checks to see that principal and object are within the same namespace or memory space or to see that a requested action is authorized for an object to be operated upon. Each program or set of programs runs in a separate context. Access from one program to another program across the context barrier can be achieved under controlled circumstances by using shared interface objects. Shared interface objects have a property that permits them to be accessed across the context barrier regardless of security restrictions that would otherwise apply. Shared interface objects, however, may enforce their own security rules independently of the context barrier.

Techniques for permitting access across a context barrier in a small footprint device using shared object interfaces

A small footprint device can securely run multiple programs from unrelated vendors by the inclusion of a context barrier isolating the execution of the programs. The context barrier performs security checks to see that principal and object are within the same context or to see that a requested action is authorized for an object to be operated upon. Each program or set of programs runs in a separate context, however, one context has access to all program modules without context barrier constraints.

Techniques for permitting access across a context barrier on a small footprint device using run time environment privileges

A small footprint device can securely run multiple programs from unrelated vendors by the inclusion of a context barrier isolating the execution of the programs. The context barrier performs security checks to see that principal and object are within the same namespace or memory space or to see that a requested action is authorized for an object to be operated upon. Each program or set of programs runs in a separate context. Access from one program to another program across the context barrier can be achieved under controlled circumstances by using a global data structure.

A small footprint device, such as a smart card, can securely run multiple programs from unrelated vendors by the inclusion of a context barrier isolating the execution of the programs. The context barrier performs security checks to see that principal and object are within the same namespace or memory space or to see that a requested action is authorized for an object to be operated upon.

A small footprint device can securely run multiple programs from unrelated vendors by the inclusion of a context barrier isolating the execution of the programs. The context barrier performs security checks to see that principal and object are within the same context or to see that a requested action is authorized for an object to be operated upon. Each program or set of programs runs in a separate context. Access from one program to another program across the context barrier can be achieved under controlled circumstances by using an entry point object.

A network computer system providing for the fault tolerant storage and retrieval of data files includes a client system connected to a data communication network that may source a first data transfer request to said data communication network for the transfer or retrieval of data. A first server system, including first medium for storing data files, is connected to the data communication network so as to be responsive to first data transfer requests. A second server system, including second medium for storing data files is also connected to said data communication network to also be responsive to first data transfer requests. A control protocol, established between the first and second server systems, coordinates an asymmetric response by the first and second server systems to a first data transfer request, such that file data transferred by the client with the first data transfer request is replicated to the first and second storing mediums and such that file data transferred to the client system in response to the first data transfer is non-replicatively provided to the client system by either the first or second server system.

Growing community of inventors

Sunnyvale, CA, United States of America

Mitchel B Butler