We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

לאתר זה תהיה פונקציונליות מוגבלת בזמן שאנו מתחזקים אותו לשיפור החוויה שלך. אם מאמר מסויים לא פותר את הבעיה שלך וברצונך לשאול שאלה, קהילת התמיכה שלנו מחכה לעזור לך ב־Twitter תחת ‎@FirefoxSupport וב־Reddit תחת ‎/r/firefox.

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

How does a plugin become "known" by Firefox?

  • 4 תגובות
  • 2 have this problem
  • 7 views
  • תגובה אחרונה מאת Jimvet100

more options

In the add-in plugin check page, there are several plugins listed as "Unknown". For instance, Microsoft Office 2013,15.0.4514.1000. What does this mean as far as my use of FF is concerned? And how do I get FF to "know" them?

In the add-in plugin check page, there are several plugins listed as "Unknown". For instance, Microsoft Office 2013,15.0.4514.1000. What does this mean as far as my use of FF is concerned? And how do I get FF to "know" them?

פתרון נבחר

That one shouldn't affect your use of Firefox or affect your security.

The Plugin Check was instituted mainly due to Adobe Flash and Sun/Oracle Java having so many reported security faults that "they" ignored for years, that when "they" started to fix them the rate of new versions got to the point of being every month or so it became more important to Mozilla to be able to alert their users about plugins that needed to be updated. So the Plugin Check system was instituted. QuickTime was a concern, too, along with other audio / video plugin programs; but of lesser importance as "they" weren't as "exploitable" or weren't being used for exploits or anywhere near as often.

As far as those that come up as "unknown", most are not considered a security issue. Although some (mostly made by Microsoft) like Silverlight aren't as readily identifiable thru the registry by Firefox; look at your "Installed Plugins" in the More system details... and you'll see 5.1.30214.0 - that is the Silverlight plugin. Not enough discoverable information for Firefox to ID it from the Registry and show it in Firefox, but the Plugin Check page does know what it is.

Read this answer in context 👍 2

כל התגובות (4)

more options

פתרון נבחר

That one shouldn't affect your use of Firefox or affect your security.

The Plugin Check was instituted mainly due to Adobe Flash and Sun/Oracle Java having so many reported security faults that "they" ignored for years, that when "they" started to fix them the rate of new versions got to the point of being every month or so it became more important to Mozilla to be able to alert their users about plugins that needed to be updated. So the Plugin Check system was instituted. QuickTime was a concern, too, along with other audio / video plugin programs; but of lesser importance as "they" weren't as "exploitable" or weren't being used for exploits or anywhere near as often.

As far as those that come up as "unknown", most are not considered a security issue. Although some (mostly made by Microsoft) like Silverlight aren't as readily identifiable thru the registry by Firefox; look at your "Installed Plugins" in the More system details... and you'll see 5.1.30214.0 - that is the Silverlight plugin. Not enough discoverable information for Firefox to ID it from the Registry and show it in Firefox, but the Plugin Check page does know what it is.

more options

Only a few commonly used plugin are recognized the the plugin check website.

You can search this JavaScript file for mimeType: to see which plugins are supported (Highlight All makes it easier to spot them).

Among them are: Java, Shockwave Flash, Shockwave for Director, Windows Media Player, Silverlight, VLC, Adobe Reader, RealPlayer.

השתנתה ב־ על־ידי cor-el

more options

Thank you for your help; I think I now understand the situation. I have marked it "Solved". Onward.

more options

Thanks for the info. I consider it "solved".