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!

Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Avatar for Username

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

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

  • 1 svar
  • 3 har dette problem
  • 1 visning
  • Seneste svar af Kuib

Kuib
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?

Valgt løsning

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?

Læs dette svar i sammenhæng 👍 0

Alle svar (1)

Kuib
Kuib Spørgsmålsstiller
more options

Valgt løsning

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?