Eolas Technologies Incorporated v. Adobe Systems Incorporated et al

Filing 393

NOTICE by Google Inc., YouTube, LLC re 367 Opposed MOTION Adobe Systems Incorporated's Opposed Motion Requesting Case Management Conference To Address Plaintiff Eolas's Infringement Contentions Or, In The Alternative, To Strike Those Contentions and Motion For Expedited Consideratio and Identification of Related Issues to be Addressed (Attachments: # 1 Declaration of M. Francis, # 2 Exhibit 1, # 3 Exhibit 2, # 4 Exhibit 3, # 5 Exhibit 4, # 6 Exhibit 5, # 7 Exhibit 6, # 8 Exhibit 7, # 9 Exhibit 8, # 10 Exhibit 9, # 11 Exhibit 10, # 12 Exhibit 11, # 13 Exhibit 12, # 14 Exhibit 13, # 15 Exhibit 14, # 16 Exhibit 15, # 17 Exhibit 16, # 18 Exhibit 17, # 19 Exhibit 18, # 20 Exhibit 19, # 21 Exhibit 20, # 22 Exhibit 21, # 23 Exhibit 22, # 24 Exhibit 23)(Jones, Michael)

Eolas Technologies Incorporated v. Adobe Systems Incorporated et al

Doc. 393 Att. 9

Exhibit 8

Dockets.Justia.com

ADOBE® FLASH® PLAYER 10.1
Administration Guide

© 2010 Adobe Systems Incorporated. All rights reserved.
Copyright

Adobe® Flash® Player 10.1 Administration Guide This user guide is protected under copyright law, furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. This user guide is licensed for use under the terms of the Creative Commons Attribution Non-Commercial 3.0 License. This License allows users to copy, distribute, and transmit the user guide for noncommercial purposes only so long as (1) proper attribution to Adobe is given as the owner of the user guide; and (2) any reuse or distribution of the user guide contains a notice that use of the user guide is governed by these terms. The best way to provide notice is to include the following link. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/ Adobe, the Adobe logo, ActionScript, Flash, Flash Builder, Flex, Flex Builder are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Macintosh and Mac OS are trademarks of Apple Inc., registered in the U.S. and other countries. Microsoft, ActiveX, Windows, Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. openSUSE is a registered trademark of Novell, Inc. in the United States and other countries. PowerPC is a trademark of International Business Machines Corporation in the United States, or other countries, or both. Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and other countries. Solaris is a trademark or registered trademark of Oracle and/or its affiliates. All other trademarks are the property of their respective owners. Updated Information/Additional Third Party Code Information available at http://www.adobe.com/go/thirdparty. Portions include software under the following terms: MPEG Layer-3 audio compression technology licensed by Fraunhofer IIS and Thomson Multimedia (http://www.iis.fhg.de/amm/) This software is based in part on the work of the Independent JPEG Group. Speech compression and decompression technology licensed from Nellymoser, Inc. (www.nellymoser.com). Video in Flash Player is powered by On2 TrueMotion video technology. © 1992-2005 On2 Technologies, Inc. All Rights Reserved. http://www.on2.com. This product contains either BSAFE and/or TIPEM software by RSA Security, Inc.

Sorenson SparkTM video compression and decompression technology licensed from Sorenson Media, Inc. Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA. Notice to U.S. Government End Users. The Software and Documentation are "Commercial Items," as that term is defined at 48 C.F.R. §2.101, consisting of "Commercial Computer Software" and "Commercial Computer Software Documentation," as such terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein. Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA 95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of 1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60, 60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.

Last updated 6/10/2010

iii

Contents
Chapter 1: Introduction Why install Flash Player? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Additional resources .................................................................................................. 1

Chapter 2: Flash Player environment Player files and locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Data formats used Player processes Player versions ..................................................................................................... 4 ............................................................................................... 5 ....................................................................................................... 6 ........................................................................................................ 6 Network protocols used

Chapter 3: Player installation Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Uninstalling Flash Player EXE installation Configuring SMS ............................................................................................... 7 ........................................................................................... 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 ........................................................................................................ 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Active Directory installation

SMS and Adobe Catalog installation Interactive MSI installation using SMS Command line MSI installations Windows registry keys DMG installation for Macintosh Customizing player behavior Additional resources

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Troubleshooting installation problems

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 4: Administration Privacy and security settings (mms.cfg) The Global FlashPlayerTrust directory

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 5: User-configured settings Accessing user settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Privacy options Update options Security options Display options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Local storage options

The User FlashPlayerTrust directory

Chapter 6: Security considerations Security overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Security sandboxes for local content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 About compatibility with previous Flash Player security models Data loading through different domains

Last updated 6/10/2010

FLASH PLAYER ADMINISTRATION GUIDE
Contents

iv

Additional security resources

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Last updated 6/10/2010

1

Chapter 1: Introduction
Why install Flash Player?
Adobe® Flash® Player is the software that allows computers to play multimedia content contained in SWF (pronounced "swiff") files, which are the main type of file used by Flash Player. This content can be created by Adobe® Flash® Professional, Adobe® Flex® BuilderTM, or other tools that output the SWF file format. SWF content can range from simple animations to online advertisements to complete applications that communicate over the Internet. Flash Player is available in multiple forms. In its most popular form, it is embedded in a web browser as a plug-in or an ActiveX control. You may have been asked to deploy Flash Player in your network environment because someone in your company has built a SWF application for business use, or because there is external SWF content that employees want to have access to. To deploy the player, you must first acquire a license to do so. Distribution licenses are free of charge and can be acquired through the online licensing application at www.adobe.com/licensing/distribution. For answers to questions regarding Flash Player licensing and deployment, see the Adobe Player Distribution FAQ at www.adobe.com/licensing/distribution/faq.

Additional resources
The following sites provide information about some general topics related to the Flash Platform, Flash Player, and design and development tools. For information about sites related specifically to issues covered in this document, see the chapter that covers that issue. For example, for an extensive list of resources specific to the topic of security, see "Additional security resources" on page 40 in "Security considerations" on page 36. For the latest version of this guide, see the Adobe Flash Player Administration Guide section of the Flash Player Developer Center at www.adobe.com/go/flash_player_admin.

Flash Player and deployment
The following sites contain information and links to help you understand how to deploy Flash Player and work with SWF files.

· The Flash Player Support Center at www.adobe.com/support/flashplayer/ provides information on a number of topics relating to installing, using, and deploying Flash Player. It also contains links to documents that can answer just about any question you might have about Flash Player, locations for downloading the player, user forums, and so on. Much of the information in this document is excerpted from documents available from the Support Center. · The Flash Player Developer Center at www.adobe.com/devnet/flashplayer provides extensive information about Flash Player, including development and deployment of applications. The content includes Tech Notes, articles, and tutorials. · The SWF File Format Specification at www.adobe.com/go/swf_file_format documents the SWF file format and describes how to write SWF files. · The Flash Player Release notes at www.adobe.com/support/documentation/en/flashplayer/releasenotes.html contain information about features, fixes and improvements, and known issues for each version of the player.

Last updated 6/10/2010

FLASH PLAYER ADMINISTRATION GUIDE
Introduction

2

Design and development tools
Adobe provides the following tools for developing SWF files (the file format that executes in Flash Player):

· Adobe Flash Professional (www.adobe.com/products/flash/)
In Flash Professional, designers and developers create FLA files that contain graphical elements, a timeline, and ActionScript code. Both ActionScript 2.0 and ActionScript 3.0 are supported. FLA files are compiled into SWF files.

· Adobe® Flash® BuilderTM (www.adobe.com/products/flashbuilder/)
In Adobe® Flash® BuilderTM 4 (formerly Adobe® Flex® BuilderTM), developers and designers create MXML files and FLA files using the open source Flex framework. They can also use ActionScript 3.0. Both MXML and ActionScript compile into SWF files.

· Adobe® Flex® (www.adobe.com/products/flex/)
In Flex, developers create MXML files that describe the visual and code elements of their applications. They can also use ActionScript 3.0. Both MXML and ActionScript compile into SWF files.

Last updated 6/10/2010

3

Chapter 2: Flash Player environment
Player files and locations
Adobe Flash Player is normally deployed as a browser plug-in or ActiveX control. For each player environment, two versions of Flash Player are available--a "Content Debugger" version for developers, and a "Release" version for end users. The Content Debugger player is installed with the development environment. This player implements the same feature set as the Release player, but also displays run-time errors during compilation. Each of these implementations is described in this section. Note: There is also a stand-alone player, but it's usually installed by the development tools, not deployed by administrators.

Firefox/Mozilla plug-in architecture
Mozilla, Mozilla, Mozilla-based browsers (such as Firefox), and the Safari browser on the Macintosh use this plug-in.

Windows plug-in filenames and locations
On Windows, files named NPSWF32.dll and flashplayer.xpt are installed. These files are placed in the following directory, along with the ActiveX control. For example:
%WINDIR%\System32\Macromed\Flash

Note: The %WINDIR% location represents the Windows system directory, such as C:\WINDOWS. For 64-bit machines, the System directory is SysWow64, instead of System32. The Windows plug-in installer also places a broker application called FlashUtil10h_Plugin.exe in the same directory as the Flash Player Plug-in DLL. The 10h will change with each release, similar to the ActiveX FlashUtil file. NPSWF32_FlashUtil.exe a NPSWF32_FlashUtil.exe includes functionality required by Windows Vista, Windows 7, and as an uninstall mechanism.

Macintosh plug-in filenames and locations
On the Macintosh, files named Flash Player.plugin and flashplayer.xpt are installed. These files are placed in the Internet plug-ins folder in the Library folder.

Linux plug-in filenames and locations
On Linux, files named libflashplayer.so and flashplayer.xpt are installed. The install location is dependent upon the browser, Linux distro, and distro version.

ActiveX Control on Windows
The The ActiveX control is used by Microsoft Internet Explorer as well as certain other applications, such as Microsoft a Powerpoint and Yahoo Messenger. The player is an OCX file whose name reflects the version number and unique letter for each subsequent release (if any) of the player. For example, for the initial release of Flash Player 10, the Release player filename is Flash10a.ocx and the Content Debugger player filename is FlDbg10a.ocx. For Flash Player 10.1, both the Release and Content Debugger versions are called Flash10h.ocx. The OCX files are stored in the following directory:

Last updated 6/10/2010

FLASH PLAYER ADMINISTRATION GUIDE
Flash Player environment

4

%WINDIR%\System32\Macromed\Flash

Note: The %WINDIR% location represents the Windows system directory, such as C:\WINDOWS. For 64-bit machines, the System directory is SysWow64, instead of System32.

Additional files
When Flash Player is installed on Windows, certain utility files are installed that perform special functions for Flash Player, including auto-update notification and brokering certain processes on Windows Vista. These utility files also provide developers a way to easily switch between player versions during testing. This functionality is briefly described in this section, and more information is available in the TechNote entitled " Installation issues when switching between release and debugger versions during development and testing" at www.adobe.com/go/4da116d3. Note: In Flash Player 10.1, there are no longer any special instructions for switching between Release and Debugger Players. The tech note only applies to pre-FP10.1 Players.

FlashUtil.exe and GetFlash.exe
A utility file named FlashUtil10h_ActiveX.exe is installed with Flash Player in the %WINDIR%\System32\Macromed\Flash directory. For 64-bit machines, the System directory is SysWow64, instead of system32. The utility is versioned with the control; for example, FlashUtil10h_ActiveX.exe is installed with the control Flash10h.ocx. The FlashUtilnn.exe file is associated with the auto-update functionality, uninstallation, and brokering the interaction between the ActiveX control and Internet Explorer (brokering only occurs on Windows Vista and above). When the browser plug-in is installed, a similar application named FlashUtil10h_ActiveX.exe is installed. This file is associated only with the browser plug-in, and is separate from the FlashUtil10h_ActiveX.exe used for the ActiveX control. There is also a new file called FlashUtil10h_ActiveX.dll.

Data formats used
Several file types are created or read by Flash Player. These file types are summarized in the following list.

· SWF: The SWF file format (pronounced "swiff") is an efficient delivery format that contains vector graphics, text, video, and sound. Flash Player executes SWF files. SWF files can be loaded into Flash Player dynamically by instructions in other SWF files. · CFG: These are configuration files that network administrators and developers can deploy along with Flash Player to customize Flash Player settings and address certain security issues for all users. For more information, see "Administration" on page 19. End users can also create CFG files to address certain security issues for that specific user; see "The User FlashPlayerTrust directory" on page 35. · SWC (pronounced "swik"): These are SWF files that developers deliver as components for use when working in the Flash authoring environment. · SO: Shared object files are used by Flash Player to store data locally. For example, a developer may create a game application that stores information on high scores. This data may be stored either for the duration of a Flash Player session, or persistently across sessions. In addition, Flash Player creates a persistent shared object that stores player settings, such as the amount of disk space a web site can use, if any, when creating shared objects. Shared object files are stored in the following locations:
Windows Vista and Windows 7 C:\Users\username\Application Data\Macromedia\Flash

Player\#SharedObjects\randomDirectoryName

Last updated 6/10/2010

FLASH PLAYER ADMINISTRATION GUIDE
Flash Player environment

5

Windows 2000 and Windows XP C:\Documents and Settings\username\Application Data\Macromedia\Flash

Player\#SharedObjects\randomDirectoryName
Macintosh /Users/username/Library/Preferences/Macromedia/Flash

Player/#SharedObjects/randomDirectoryName
Linux GNU-Linux ~/.macromedia#SharedObjects/randomDirectoryName

Shared objects are stored in a directory with a randomly generated name for security purposes. Flash Player remembers how to direct a SWF file to the appropriate location, but users of other applications outside Flash Player, such as a web browser, cannot use those applications to access the data. This limitation ensures that the data is used only for its intended purpose.

· MP3 - The compressed audio file format. · JPG, PNG, and GIF- Image file formats. The TIF and BMP formats are not directly supported for use in SWF files. · FLV - Flash Player compressed video format. · FXG - Flash XML graphics format. An XML-based graphics interchange format for the Flash Platform. · XML (eXtensible Markup Language) - Used for sending and receiving larger amounts of data with structured text. · MXML - The XML-based language that developers use to lay out components in Flex applications.
Note: If you block access to any of these file types, certain functionality of Flash Player may be disabled.

Network protocols used
Flash Player can use the following network protocols:

· HTTP · HTTPS · RTMP (Real Time Messaging Protocol) - a proprietary protocol used with Flash Media Server to stream audio and video over the web. The default connection port is 1935. · RTMPT - RTMP tunneling via HTTP. The default connection port is 80. · RTMPS - RTMP tunneling via HTTPS. The default connection port is 443. (For more information about using the RTMP protocols, see the TechNote entitled "HTTP Tunneling Protocols" at www.adobe.com/go/tn_16631.) · SOAP - Simple Object Access Protocol · UNC - Universal Naming Convention · TCP/IP - Transmission Control Protocol/Internet Protocol · FTP - File Transfer Protocol · SMB - Server Message Block. SMB is a message format used by DOS and Windows to share files, directories, and devices. Flash Player can load animations and SWF files from remote SMB shares. Flash has restrictions on what Flash SWF files loaded from SMB shares are allowed to do. · SSL - Secure Sockets Layer · AMF - ActionScript Message Format

Last updated 6/10/2010

FLASH PLAYER ADMINISTRATION GUIDE
Flash Player environment

6

Player processes
Most Most often, Flash Player runs as a browser plug-in. When Flash Player operates in this mode, it does not launch any new processes on the end user's computer. When run as a stand-alone player, it launches a process named FlashPlayer.exe. The one exception to this statement is when content is played back using Internet Explorer on Windows Vista or above. In this case FlashUtil10h_ActiveX.exe will be in the process list. Flash and Flex developers can package their SWF files into stand-alone EXE files, called projectors. When a projector is run, it launches a single process, named for the projector executable filename. Other processes are created when Flash Player auto update occurs. GetFlash.exe or FlashUtil10h_ActiveX.exe will be running during an auto update request and subsequent downloading and installing of the updated player. FlashUtil10h_ActiveX.exe or FlashUtil10h_Plugin.exe processes will be visible when the Flash Player is uninstalled on Windows via Add/Remove Programs.

Player versions
Before deploying the player, you might want to know what version is already installed on an end user's machine. An easy way to determine the version of Flash Player installed is to navigate to www.adobe.com/products/flash/about; this page displays a message stating which version is installed. Or, while a SWF file is playing, right-click (Windows or Linux) or Command-click (Macintosh) on the SWF content and then choose "About Flash Player" from the context menu. On the Macintosh, you can navigate to the Flash Player.plugin file located in the /Library/Internet plug-ins folder, then Command-click and choose Get Info. The version number is available on the General menu. On Windows, you can determine which version of the ActiveX control is installed by navigating to the directory where the OCX file is located (see "ActiveX Control on Windows" on page 3 for the default location). Right-click on the OCX file and choose Properties, then inspect the value in the Version tab. If the OCX file isn't installed in the default location, you can determine its location and name by inspecting the following registry key, which is created when the OCX control is registered:
HKEY_CLASSES_ROOT\CLSID\{D27CDB6E-AE6D-11cf-96B8-444553540000}\InprocServer32

Similarly, you can determine the Plug-in version by examining the version tab of the NPSWF32.dll file, which is located in the same folder as the ActiveX control. End users can view the currently installed version by visiting www.adobe.com/products/flash/about with their browser, or by right-clicking on a SWF file and selecting "About Flash Player..." For information on how to incorporate player version detection into web sites, see the "Detection and Installation" section at the Flash Player Developer Center (www.adobe.com/devnet/flashplayer/detection_installation.html). If you want to learn which version of Flash Player is installed on an end user's machine without going to each machine individually, you or a developer at your site can create and distribute a SWF file that implements the System.Capabilities.version API and reports the results to a database using a command such as HTTP GET or POST. This technique is useful for activities such as collecting statistics on how many users have which version of Flash Player.

Last updated 6/10/2010