Comments on: New PluginCheck Page Needs Your Help

By: J. Couprie

J. Couprie — Sun, 18 Oct 2009 16:44:53 +0000

As Crashx I have same error (of course in the French version) when using “Plugin Check”.
“www-trunk.stage.mozilla.com utilise un certificat de sécurité invalide.

Le certificat n’est pas sûr car l’autorité délivrant le certificat est inconnue.

(Code d’erreur : sec_error_unknown_issuer)”.
A valid certificate should not need so long time !
This page report an acrobat reader that I have uninstalled and replaced by Foxit reader is it just an example or does it test my plugins ?
Where can I find the list of my installed plugins ? Tools does not give it !

By: Shaun

Shaun — Tue, 13 Oct 2009 11:33:58 +0000

Everything seems to be working in Ubuntu. You should have an option to elicit translations from bilingual users.

By: crashx

crashx — Sun, 11 Oct 2009 16:51:37 +0000

Is there any way to acces the site with firefox? All I get is that certificate-error (sec error unknow issuer), with no box for adding an exception. How can I manually add one?

By: Fabian

Fabian — Tue, 06 Oct 2009 02:32:00 +0000

You should check navigator.plugins[i].filename against libtotem-*-plugin.so. The browser plugins of Totem just have fake names in case a Website checks for one of those plugins. It’s not necessary to check if they are up-to-date.

I have the following installed:
VLC Multimedia Plugin (compatible Totem 2.26.3)
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so

Windows Media Player Plug-in 10 (compatible; Totem)
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so

DivX® Web Player
/usr/lib/mozilla/plugins/libtotem-mully-plugin.so
Version: 1.4.0.233; 1.4 version of the real plugin wasn’t released at all

QuickTime Plug-in 7.2.0
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so

By: ozten

ozten — Mon, 05 Oct 2009 17:01:45 +0000

We’ve captured some of the feedback here and rolled it into these changes: https://bugzilla.mozilla.org/show_bug.cgi?id=520574

By: Dan

Dan — Sat, 03 Oct 2009 21:07:05 +0000

Great idea. I only have 2 plugins here on Linux and both are up to date. Many of the Windows machines I use though have out-of-date plugins (not for lack of trying in some cases though. I’ve seen so many people ignore Adobe’s Flash updater that runs at startup…)

I hope that this page can also be used for some interesting metrics. Every time someone visits the page, record their Firefox version, their OS and what plugins they had installed. We could then get some great insights into the percentage of visitors that have a certain plugin, and how many of those have an up-to-date version of it. Plot a graph against time for each plugin, and if it’s an upwards trend, hooray!

By: ozten

ozten — Sat, 03 Oct 2009 20:08:09 +0000

@Justin – Good point, sorry I missed it. Adding another status “crashy” would be possible without much change to the system. Old and crashy – “This version is known to crash Firefox, please update” Update Now. Latest and crashy – “Known to cause Firefox crashes, no fix available” Disable Now. If a “crashy” release became vulnerable, then vulnerable would trump crashy and the status code would be updated to vulnerable.

By: Justin Dolske

Justin Dolske — Sat, 03 Oct 2009 19:54:09 +0000

@ozten – To be clear, I was talking about the case where the user has version X of a plugin installed, which is known to be crashy but isn’t actually insecure. We really really want them to upgrade to version Y; it’s just not a security/vulnerability issue.

By: James John Malcolm

James John Malcolm — Sat, 03 Oct 2009 19:42:35 +0000

Very nice, even works in Seamonkey 2(b2).

It probably would be good to
1) Include/link to it in about:plugins
2) Translate it!

By: ozten

ozten — Sat, 03 Oct 2009 19:35:52 +0000

@B.J.Herbison and @Gen Kanai – I’ll update the post with the different states a plugin can be in.