Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

silverlight 5.1.40728.0 reported by Firefox 41.0.1 as vulnerable/needs update. Where from? Why?

  • 1 Antwort
  • 3 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von Kuib

more options

Silverlight 5.1.40728.0 reported by Firefox 41.0.1 as vulnerable/'update now' when I check my plug-ins are up to date. Clicking the button takes me to MS Silverlight download site, but all I get from following instructions is same version of Silverlight and same outcome from Firefox. What is the vulnerability? Why can't Silverlight update? Am I safe to leave Silverlight as is or should I disable it? Or what? Why report it as vulnerable and needing update if there is no remedy?

Silverlight 5.1.40728.0 reported by Firefox 41.0.1 as vulnerable/'update now' when I check my plug-ins are up to date. Clicking the button takes me to MS Silverlight download site, but all I get from following instructions is same version of Silverlight and same outcome from Firefox. What is the vulnerability? Why can't Silverlight update? Am I safe to leave Silverlight as is or should I disable it? Or what? Why report it as vulnerable and needing update if there is no remedy?

Ausgewählte Lösung

I think I found the answer - it's those damn DRM vultures again pushing HTML5 equivalents cos that gives them more control over stuff we want to watch through browsers - check out this place for more info: http://www.defectivebydesign.org/what_is_drm_digital_restrictions_management See what I mean? Why not sign up?

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (1)

more options

Ausgewählte Lösung

I think I found the answer - it's those damn DRM vultures again pushing HTML5 equivalents cos that gives them more control over stuff we want to watch through browsers - check out this place for more info: http://www.defectivebydesign.org/what_is_drm_digital_restrictions_management See what I mean? Why not sign up?