plugin check not working
The Firefox plugin checker is reporting "vulnerable - Update Now" for my Java Deployment Toolkit 7.0.510.13. and Java(TM) Platform SE 7 U51 plugins.
The 'update now' link takes me to the Java download page which invites me to download the latest Plugin 7.51. but i already have 7.51 installed so the plugin checker is incorrectly displaying "vulnerable - Update Now". I have had 7.51 installed since January 17th and run the plugin checker on a weekly basis so i'm not sure why it has suddenly decided that this is a vulnerable plugin.
I am running Firefox 28.0 on Windows 7
You wrote the following in bug 1023889
MetaStream 3 Plugin reported Viewpoint Plugin vulnerable 22.214.171.124 "Update Now". When i clicked "update now" it went to a dead link http://www.viewpoint.com/technologies/viewpoint-media-player.shtml
I vaguely remembered reading someing on that plugin so I did a google search and found the following: https://addons.mozilla.org/en-US/firefox/blocked/p32 Viewpoint has been blocked for your protection. ...which links to: Bug 539282 - Blocklist the viewpoint plugin
I would remove (or disable) that plugin and uninstall the Viewpoint Media Player program from your computer based on the above and this wikipedia article:
P.S. More here on Viewpoint's MetaStream 3 plugin:
/questions/753880 metastream 3 plugin 126.96.36.199 has been disabled due to security or stability issues, what do we do?
See also: /questions/976775 Why is Metastream plug-in listed when I do a Plug-in Check on what plugins are up to date, I thought it was blocked?
由 AliceWyman 於 修改
If it is blocklisted, shouldn't Firefox be flagging it up when it runs plugin check?
For example, I have a Java Development Toolkit plugin which flags up "Firefox has prevented the unsafe plugin '"Java Development Toolkit' from running on www.mozilla.org"
Having re-checked, this plugin is already disabled on my machine, but i think the bug report should still exist as it is still a false "update now" to a dead link.
由 richlaughlin 於 修改
richlaughlin, You asked, If it is blocklisted, shouldn't Firefox be flagging it up when it runs plugin check?
Good question but I think you should ask it in the PluginCheck bug you filed.