NPAPI

Netscape Plugin Application Programming Interface (NPAPI) is a cross-platform plugin architecture used by many web browsers.

It was first developed for the Netscape family of browsers starting with Netscape Navigator 2.0 but was subsequently implemented by many other browsers, including all of the browsers most commonly used today (although Internet Explorer supported it until version 5.5SP2^[1][2][3]).

A plugin declares that it handles certain content types (e.g. "audio/mp3") through exposed file information. When the browser encounters such content type it loads the associated plugin, sets aside the space within the browser content for the plugin to render itself and then streams data to it. The plugin is then responsible for rendering the data as it sees fit, be it visual, audio or otherwise. So a plugin runs in-place within the page, as opposed to older browsers that had to launch an external application to handle unknown content types.

The API requires each plugin to implement and expose a comparatively small number of functions. There are approximately 15 functions in total for initializing, creating, destroying, and positioning plugins. The NPAPI also supports scripting, printing, full screen plugins, windowless plugins and content streaming.

History

The origin of the Netscape plugin functionality started not within Netscape, but at Adobe Systems. John Warnock, CEO of Adobe, and Allan Padgett, one of the primary authors of Acrobat Reader, were hopeful that Adobe's fledgling PDF file format could play a role beyond the desktop. Therefore, soon after Netscape released the first version of Navigator, Padgett and fellow developer Eshwar Priyadarshan tried to find a way to make PDF an integral part of the Web experience. The result was a live demo shown to Warnock and Jim Clark, the CEO of Netscape. Prior to that demo, the only native file formats on the Web were HTML pages and the images embedded within them. Links to any other file type caused the user to be prompted to download the file, after which the user could open the file in the appropriate application. In that demo, however, when a user clicked on a link to a PDF file, the file instantly opened within the browser window, seamlessly blending HTML and PDF consumption. Clark excitedly asked who at Netscape had provided support for the integration, only to discover that the integration was done without Netscape involvement, but with a bit of reverse engineering of the Netscape browser.

The companies set out the next week to bring what was known as "Allan's Hack" to market. While Netscape was ready to incorporate PDF directly into the browser, and certainly Adobe would have gained from that, Padgett proposed a different approach, a plugin architecture. Adobe developers Gordon Dow and Nabeel Al-Shamma had recently added a plugin architecture to the Acrobat Reader to leverage the development efforts of developers outside of the Reader team. Padgett had been a part of that effort, and he expected that if given a chance, other companies (and hopefully teams within Adobe) would choose to extend the Web as well. Clark and team in the end were convinced and set off designing the API that would support the new model.

Scripting support

Plugin scriptability is a feature allowing JavaScript code in a web page to interact with the plugin. Various versions of Netscape and then Mozilla supported this feature using different technologies: LiveConnect, XPConnect, and npruntime.

LiveConnect

Main article: LiveConnect

With Netscape 4, the NPAPI was extended to allow plugins to be scripted. This ability was known as LiveConnect. A plugin could implement and return an instance to a Java class. The public methods exposed by this class was the scriptable interface for the plugin. The class could be called from JavaScript and even from other Java applets running within the page with the browser marshalling the calls between the various contexts.

The disadvantage of LiveConnect was that it was tied heavily to the built-in version of Java within the Netscape browser. This prevented the browser from using other Java runtimes, and added a massive amount of bloat to the browser download size since it required Java to script plugins.

Additionally, LiveConnect was tricky to program. The developer had to define a Java class for the plugin, run it through a specialised Java header compiler and implement the native methods. Handling strings, exceptions and other Java objects from C++ was fraught and non-obvious. To compound matters LiveConnect used an earlier and now obsolete API for invoking native C++ calls from Java called JRI. The JRI technology has long been supplanted by JNI.

XPConnect

Main article: XPConnect

LiveConnect proved extremely problematic for Mozilla. The dependency on an obsolete and proprietary Java runtime and the JRI API meant that LiveConnect never really worked.

Mozilla was already using XPCOM to define the interfaces to many objects implemented in C++. Each interface was defined by an IDL file, and run through an IDL compiler that produced header files and a language neutral type library that was a binary representation of the interface. This binary described the interface, the methods, the parameters, the data structures and enumerations.

XPConnect uses the type library information to marshal calls between different thread contexts and between JavaScript and natively compiled C++. As XPConnect is used extensively throughout Mozilla, it is extremely robust, supported and well understood. Starting with Netscape 6.1 and Mozilla 0.9.2, the NPAPI was extended so that a plugin could return a scriptable interface to itself and XPConnect would marshal calls to it from JavaScript and the C++ implementation.

This removed the Java dependency, however there are issues with XPConnect. In particular, the technology is heavily based on XPCOM, which is similar to Microsoft COM. Thus the plugin developer must be familiar with reference counting, interfaces, IDL and so forth to implement scripting. Additionally, the dependency on XPCOM led to certain dynamic linking issues (e.g. the fragile base class problem) which had to be solved before the plugin would work correctly with different browsers. XPCOM has since been changed so that it supplies a statically linked version to address such issues. This approach also requires an .xpt file to be installed next to the DLL; otherwise the plugin will appear to work, but scripting won't, causing confusion.

NPRuntime

At the end of 2004, all major browser companies using NPAPI agreed on NPRuntime^[4] as an extension to the original NPAPI to supply scripting, via an API that is similar in style to the old C-style NPAPI and is independent of other browser technologies like Java or XPCOM. It is supported by the latest generation of Mozilla (1.7.5+) / Firefox, Safari, and Opera.

Browser support

The following web browsers support NPAPI plugins:

• Epiphany
• Google Chrome
• Safari
• Espial TV Browser
• Konqueror
• Mozilla project applications, including
  • Camino
  • Firefox
  • Mozilla Application Suite
  • SeaMonkey
• Netscape Navigator and Communicator
• Opera
• Internet Explorer up to 5.5SP2

Internet Explorer did for a time support NPAPI plugins, allowing plugins that functioned in Netscape navigator to also function in Internet Explorer. This was due to a small ActiveX control implemented within a "plugin.ocx" file that acted as a shim between ActiveX and the NPAPI plugin. IE would load the control and use it to host plugins specified within the page. However, Microsoft made the claim that the NPAPI plugins (or the IE implementation of the API) were a security issue and dropped support for them in version 5.5 SP2.^[1][2][3]

Security

A popular misconception concerning the NPAPI technology is that a plugin is somehow inherently safer than an ActiveX control. Both run native machine instructions with the same privileges as the host process. If the host processes have the same privileges, a malicious plugin can do as much damage as a malicious ActiveX control.^{[citation needed]} It is important to note that NPAPI plugins can be made much safer by simply changing user accounts. It is generally possible to install and run plugins with a limited user while installing ActiveX controls requires administrative privileges. With limited privileges, the plugin cannot do as much damage.

One important difference between NPAPI and ActiveX is that NPAPI is solely for Internet plugins, while ActiveX is used for a wide variety of purposes, including application composition in windows applications. A typical Windows user has a vast array of ActiveX controls installed, a number of which are probably marked "safe for scripting", but are not actually secure. Any of these can be used as means to subvert the user's computer.^[5]

Another difference for the NPAPI is that implementations (prior to Mozilla Firefox, see below) did not automatically download or install missing plugins. A missing plugin caused the browser to display a jigsaw piece representing the plugin. If the user clicked on that they were directed to Netscape's plugin finder service where they could manually download and install the plugin for themselves. While this is inconvenient to the user, it is also an important security measure since it prevented the content using the browser as a vector for malware.

In Internet Explorer, the HTML content specifies the location where the ActiveX control resides. If the control is not already installed, IE will automatically download and install the control from the specified source, pausing only to show the digital signature to the user and obtain their consent for installation to start. For legitimate controls, this offers a more streamlined installation mechanism with minimal user interaction. However malicious content could convince the user with clever social engineering to ignore warnings (or their better judgement) and install something that might harm their privacy or the machine. A number of spyware, adware and malware sites use this mechanism to deploy executable content to machines. Microsoft has had to increase the default security settings for ActiveX and maintain blacklists of malicious controls in an attempt to mitigate this risk.

Mozilla Firefox attempts to present a middle ground. If a plugin is missing, it will notify the user that the plugin is missing and initiate a secure connection to a plugin finder service hosted on mozilla.org. The user can permit Firefox to download and install the plugin. This model prevents content specifying where a plugin should be downloaded from – the plugin finder service does. This enables Firefox to present a fairly seamless installation mechanism but limit the service to trusted and compatible plugins from reliable sources. This model implicitly trusts the plugin finder service to return "good" plugins, increasing the security required on the host site.

PPAPI

On August 12, 2009 a page on Google Code introduced a new project, Pepper with associated Pepper Plugin API (PPAPI)^[6], "a set of modifications to NPAPI to make plugins more portable and more secure"^[7]. This extension is designed specifically to ease the implementation of out-of-process plugin execution. Further, the goals of the project are to provide a framework for making plugins fully cross-platform. Topics considered include:

• Uniform semantics for NPAPI across browsers.
• Execution in a separate process from the renderer/browser itself.
• Standardize rendering using the browser's compositing process.
• Defining standardized events, and 2D rasterization functions.
• Initial attempt at providing 3D graphics access.
• Plugin registry.

As of May 13, 2010, Google's open source browser, Chromium, is the only web browser that utilizes the new browser plug-in model ^[8]. Mozilla has announced that they are "not interested in or working on Pepper at this time."^[9]

References

1. ^ ^{a b} Netscape-style plug-ins do not work after upgrading Internet Explorer
2. ^ ^{a b} Giannandrea, J. (September 4, 2001) Microsoft breaks Web Plugins in Windows XP.
3. ^ ^{a b} Description of Internet Explorer Support for Netscape-Style Plug-ins
4. ^ NPRuntime
5. ^ CWE-623: Unsafe ActiveX Control Marked Safe For Scripting
6. ^ [1]
7. ^ Pepper.wiki
8. ^ Google heats up native code for Chrome OS
9. ^ NPAPI:Pepper - MozillaWiki

External links

• Plugin development documentation on Mozilla Developer Center, including the NPAPI API
• Hello World example of a NPAPI plugin
• An ActiveX control that hosts plugins – A replacement for plugin.ocx that was removed from Internet Explorer.
• Cross-platform NPAPI wrapper classes provided by JUCE framework
• Book on Programming Netscape Plug-Ins by Zan Oliphant
• Nixysa: A glue code generation framework for NPAPI plugins. Apache 2.0 license.
• NPAPI Tutorial Building a Firefox Plugin (Part two, Part three)
• Firebreath, a cross-platform framework that builds NPAPI and ActiveX plugins from the same codebase