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.

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

Bug in Plugin Check's status report is a security problem

  • 2 svar
  • 1 har dette problem
  • 7 visninger
  • Seneste svar af n0diamond

more options

Plugin Status (https://www.mozilla.org/en-US/plugincheck/) says "Java(TM) Platform SE 7 U65" "Up to Date 10.65.2.20". This is wrong. I have already started installing U67 because U65 is obsolete. The false report likely persuades users not to update.

Plugin Status also says "Java Deployment Toolkit 7.0.650.20" "Up to Date 10.65.2.20". I don't know yet if that is true or not. If the Platform update doesn't also update the Deployment Toolkit then I'll try to find that update. This is a big security problem because a different page reports that Java Deployment Toolkit 7.0.650.20 has a known vulnerability.

Plugin Status (https://www.mozilla.org/en-US/plugincheck/) says "Java(TM) Platform SE 7 U65" "Up to Date 10.65.2.20". This is wrong. I have already started installing U67 because U65 is obsolete. The false report likely persuades users not to update. Plugin Status also says "Java Deployment Toolkit 7.0.650.20" "Up to Date 10.65.2.20". I don't know yet if that is true or not. If the Platform update doesn't also update the Deployment Toolkit then I'll try to find that update. This is a big security problem because a different page reports that Java Deployment Toolkit 7.0.650.20 has a known vulnerability.

Alle svar (2)

more options

There is a bug on file for that, I would track the changes there: https://bugzilla.mozilla.org/show_bug.cgi?id=1052877

more options

There are several bugs in that bug report and it's still buggy. Thank you for pointing me to it though.