PluginUpdating: Difference between revisions

Jump to navigation Jump to search
Line 29: Line 29:
This page will do a check on common plug-ins and see if they are vulnerable or not. [http://www.guninski.com/mozbugs/plug-test.html An example implementation can be found here.]
This page will do a check on common plug-ins and see if they are vulnerable or not. [http://www.guninski.com/mozbugs/plug-test.html An example implementation can be found here.]


The plug-ins:
Plug-ins to check:
* Java (system update)
* [http://java.com/en/download/installed.jsp?detect=jre&try=1 Java] (system update)
* Flash (provides API, system update)
* [http://www.adobe.com/shockwave/welcome/ Flash] (provides API, system update)
* Windows media player (no idea)
 
Future plug-ins to check:
* Windows media player (system update)
* Real player (system update)
* Quicktime (system update)
* Quicktime (system update)
* Real player (system update)
 


== Mock-up ==
== Mock-up ==
Line 53: Line 56:
== Determining the latest secure version ==
== Determining the latest secure version ==
Ideally we would talk to the upstream provider and get the latest secure version. However, initially we can just maintain a file that includes the latest versions of the plug-ins.
Ideally we would talk to the upstream provider and get the latest secure version. However, initially we can just maintain a file that includes the latest versions of the plug-ins.
== We found an insecure plug-in, now what? ==
After we detect that a plug-in is out of date, we should open the vendor page in a new tab.
One major concern is that each plug-in update needs a browser restart.
=== Java ===
[http://java.com/en/download/installed.jsp?detect=jre&try=1 Sun provides an update check]. Linking here should provide a sufficient starting point for getting java up to date.
=== Flash ===
[http://www.adobe.com/shockwave/welcome/ Adobe provides an update check]. The user will be offered to navigate to this page for the update.


= References =
= References =
334

edits

Navigation menu