# US 2013/0159394 A1 · Safe Browser Plugins Using Native Code Modules

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0159394 A1
- Document ID: US20130159394A1
- Status: Published application
- Kind: A1
- Application number: 13/688,776
- Filed: 2012-11-29
- Published: 2013-06-20
- Earliest claimed: 2008-11-10
- Assignees: Google Inc.
- Inventors: Antoine LABOUR; Matthew Papakipos; Shiki Okasaka; Jeffrey R. Timanus
- Web page: https://patentgrep.com/patent/US20130159394A1

## CPC

- G06F 9/44526: {Plug-ins; Add-ons}
- G06F 16/95: Retrieval from the web
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Some embodiments provide a system that executes a plugin for a web browser. During operation, the system obtains the plugin as a native code module and executes the native code module in a secure runtime environment. Next, the system enables communication between the native code module and the web browser by providing an interface bridge between the native code module and the web browser.

## Claims

### Claim 1

A method for facilitating execution of a plugin for a web browser, comprising:
providing an interface bridge between a native code module which implements the plugin and the web browser to enable communication between the native code module and the web browser; and
executing the native code module in the secure runtime environment.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
enabling communication between the native code module and an incompatible web browser with an incompatible plugin architecture by providing a second interface bridge between the interface bridge and the incompatible web browser.

### Claim 3 (depends on 2)

The method of claim 2, wherein the web browser and the incompatible web browser are associated with at least one of a Netscape Plugin Application Programming Interface (NPAPI) plugin architecture and an ActiveX plugin architecture.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
validating the native code module prior to executing the native code module in the secure runtime environment.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
enabling communication between the native code module and other plugins for the web browser using a shared memory interface between the native code module and the other plugins.

### Claim 6 (depends on 1)

The method of claim 1, wherein the interface bridge is implemented using at least one of, a remote procedure call (RPC) mechanism, a socket and a shared memory.

### Claim 7 (depends on 1)

The method of claim 1, wherein providing the interface bridge between the native code module and the web browser involves using an inter-module communication (IMC) runtime.

### Claim 8 (depends on 7)

The method of claim 7, wherein communication between the native code module and the web browser over the IMC runtime is implemented using a proxy and a stub.

### Claim 9 (depends on 8)

The method of claim 8, wherein the proxy and the stub are used to reach objects associated with the native code module or the web browser.

### Claim 10

A system for executing a plugin for a web browser, comprising:
a secure runtime environment configured to execute a native code module which implements the plugin; and
an interface bridge between the native code module and the web browser, wherein the interface bridge is configured to enable communication between the native code module and the web browser.

### Claim 11 (depends on 10)

The system of claim 10, further comprising:
a second interface bridge between the interface bridge and an incompatible web browser with an incompatible plugin architecture, wherein the second interface bridge is configured to enable communication between the native code module and the incompatible web browser.

### Claim 12 (depends on 11)

The system of claim 11, wherein the web browser and the incompatible web browser are associated with at least one of a Netscape Plugin Application Programming Interface (NPAPI) plugin architecture and an ActiveX plugin architecture.

### Claim 13 (depends on 10)

The system of claim 10, further comprising:
a validator configured to validate the native code module prior to executing the native code module.

### Claim 14 (depends on 10)

The system of claim 10, further comprising:
a shared memory interface configured to enable communication between the native code module and other plugins for the web browser.

### Claim 15 (depends on 10)

The system of claim 10, wherein the interface bridge is implemented using at least one of, a remote procedure call (RPC) mechanism, a socket and a shared memory.

### Claim 16 (depends on 10)

The system of claim 10, wherein providing the interface bridge between the native code module and the web browser involves using an inter-module communication (IMC) runtime.

### Claim 17 (depends on 16)

The system of claim 16, wherein communication between the native code module and the web browser over the IMC runtime is implemented using a proxy and a stub.

### Claim 18 (depends on 17)

The system of claim 17, wherein the proxy and the stub are used to reach objects associated with the native code module or the web browser.

### Claim 19

A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for facilitating execution of a plugin for a web browser, the method comprising:
providing an interface bridge between a native code module which implements the plugin and the web browser to enable communication between the native code module and the web browser; and
executing the native code module in the secure runtime environment.

### Claim 20 (depends on 19)

The computer-readable storage medium of claim 19, wherein the method further comprises:
enabling communication between the native code module and an incompatible web browser with an incompatible plugin architecture by providing a second interface bridge between the interface bridge and the incompatible web browser.

### Claim 21 (depends on 20)

The computer-readable storage medium of claim 20, wherein the web browser and the incompatible web browser are associated with at least one of a Netscape Plugin Application Programming Interface (NPAPI) plugin architecture and an ActiveX plugin architecture.

### Claim 22 (depends on 19)

The computer-readable storage medium of claim 19, wherein the method further comprises:
validating the native code module prior to executing the native code module in the secure runtime environment.

### Claim 23 (depends on 19)

The computer-readable storage medium of claim 19, wherein the method further comprises:
enabling communication between the native code module and other plugins for the web browser using a shared memory interface between the native code module and the other plugins.

### Claim 24 (depends on 19)

The computer-readable storage medium of claim 19, wherein the interface bridge is implemented using at least one of, a remote procedure call (RPC) mechanism, a socket and a shared memory.

### Claim 25 (depends on 19)

The computer-readable storage medium of claim 19, wherein providing the interface bridge between the native code module and the web browser involves using an inter-module communication (IMC) runtime.

### Claim 26 (depends on 25)

The computer-readable storage medium of claim 25, wherein communication between the native code module and the web browser over the IMC runtime is implemented using a proxy and a stub.

### Claim 27 (depends on 26)

The computer-readable storage medium of claim 26, wherein the proxy and the stub are used to reach objects associated with the native code module or the web browser.
