Firefox/Projects/Plugin Update Referrals: Difference between revisions
Jump to navigation
Jump to search
(→Bugs) |
(→Design) |
||
| Line 23: | Line 23: | ||
* On the Plugins tab of the extension manager, there would be a "Check for updates" button. Clicking this would open a tab to the outdated plugins page. Additionally, the items for outdated plugins would indicate that they're outdated. | * On the Plugins tab of the extension manager, there would be a "Check for updates" button. Clicking this would open a tab to the outdated plugins page. Additionally, the items for outdated plugins would indicate that they're outdated. | ||
Future improvements: | |||
* When the blocklist service updates from a periodic check and detects an outdated plugin (that hasn't been warned of before), it shows an alert (via the alerts service) informing the users. Clicking on this alert would open a tab to the plugins page on mozilla.com. | * When the blocklist service updates from a periodic check and detects an outdated plugin (that hasn't been warned of before), it shows an alert (via the alerts service) informing the users. Clicking on this alert would open a tab to the plugins page on mozilla.com. | ||
Revision as of 02:11, 28 September 2009
Overview
Our goal is to get as many people who use Firefox to also update their plugins to improve the security of their systems. We want to do this in the Firefox 3.6 time frame. Suggested path is:
- Maintain a list of common plugins and versions.
- Offer a page on mozilla.com that checks plugin versions and offers links to updated versions of those plugins.
- Use the plugin blocklist capabilities in Firefox to push users to update.
Non-goals
- Automatic downloading and updating of plugins
Design
The browser should use the existing blocklist functionality in order to figure out if someone has old plugins installed.
The user would be notified in the following ways:
- User visits a page with an outdated plugin. The plugin is allowed to load. A notification box is shown in that tab, informing user that the plugin is outdated. There's an "Update Plugins..." button, that takes the user to the page on mozilla.com. This page would list all outdated plugins the user has installed, not just the one that was just used.
- When the user manually checks for updates via Help -> Check for Updates, and there is no update, it then checks for outdated plugins. If there are any, provide a link to the mozilla.com page.
- On startup (not after an update), if outdated plugins are detected, open a tab to the outdated plugins page. This would only happen once for a plugin version.
- On the Plugins tab of the extension manager, there would be a "Check for updates" button. Clicking this would open a tab to the outdated plugins page. Additionally, the items for outdated plugins would indicate that they're outdated.
Future improvements:
- When the blocklist service updates from a periodic check and detects an outdated plugin (that hasn't been warned of before), it shows an alert (via the alerts service) informing the users. Clicking on this alert would open a tab to the plugins page on mozilla.com.
Progress
See Plugins:PluginCheck for updates on the website and service side of this problem.
See Security:ThePluginProblem for some thoughts from Chris Hofmann on the topic.
Web Site
Service
morgamic leading.
- Still under design, see documentation
Server bugs:
Partners
- Kev not in the loop yet. Need to work with at least:
- Apple (Quicktime)
- Adobe (Flash, Shockwave, Reader)
- Microsoft (Silverlight)
- DivX
- Sun (Java)
Firefox
- Integration with mozilla.com not spec'd.
- Initial experience not spec'd.