Update plugincheck for Silverlight 5.1.20125.0 on Windows and Mac

RESOLVED FIXED

Status

Websites
plugins.mozilla.org
--
critical
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Rob, Assigned: Tomcat)

Tracking

({qawanted})

Details

(URL)

(Reporter)

Description

5 years ago
Microsoft released Silverlight 5.1.20125.0 today.

-----

Silverlight -- Version: 5.1.20125.0   Date published: 3/12/2013 
This security update is rated Critical for Microsoft Silverlight 5 and Microsoft Silverlight 5 Developer Runtime when installed on Mac and all supported releases of Microsoft Windows

Security Update for Microsoft Silverlight (KB2814124)
http://www.microsoft.com/en-us/download/details.aspx?id=36946

KB articles: KB2814124 
http://support.microsoft.com/kb/2814124
Security bulletins: MS13-022 -- "Vulnerability in Silverlight could allow remote code execution."
http://technet.microsoft.com/en-us/security/Bulletin/MS13-022

-----

Recently (Bug 850212) we had a critical Update for Flash and now one for Silverlight, on the same day; yet the PlugInCheck Page (https://www.mozilla.org/en-US/plugincheck/) said all was OK.


We need to automate things a little (lot?). Rather than checking every possible Website or burdening the Maintainers with an infinite List of Subscriptions we can do things locally with more than a modicum of success.


All we need to do is have the Script running on the Server check if ANY User has a newer version of the Plugin installed than what the Script thinks is the newest version. When that occurs ONE mail can be sent to a small List of Maintainers, and they can manually check if our Script on the Server is OK or if it needs to be updated. A second mail could be sent the next day and/or the Maintainer could flag that Version for skipping (beta, not publicly available, data error, etc.).

This method is almost certain to work in every case. Only if no one obtains Updates, and subsequently does a PlugInCheck, could one of the Plugins slip by. It is certainly better than what we have now.


Thanks.


PS: I CC'd the last two People who were involved in the Silverlight Plugin Update a few months ago, I hope that was helpful.

Comment 1

5 years ago
(In reply to Rob from comment #0)
> We need to automate things a little (lot?). Rather than checking every
> possible Website or burdening the Maintainers with an infinite List of
> Subscriptions we can do things locally with more than a modicum of success.
That part needs a new bug marked as a dependency of the new plugincheck, bug 821279.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Summary: Update plugincheck for Silverlight 5.1.20125.0 on Windows → Update plugincheck for Silverlight 5.1.20125.0 on Windows and Mac
Version: Trunk → unspecified
(Assignee)

Comment 2

5 years ago
pushed to production, raymond: we need also a qa check here.thanks!
Assignee: nobody → cbook
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Keywords: qawanted
Resolution: --- → FIXED
(Reporter)

Comment 3

5 years ago
(In reply to Scoobidiver from comment #1)
> (In reply to Rob from comment #0)
> > We need to automate things a little (lot?). Rather than checking every
> > possible Website or burdening the Maintainers with an infinite List of
> > Subscriptions we can do things locally with more than a modicum of success.
> That part needs a new bug marked as a dependency of the new plugincheck, bug
> 821279.

Filed as Bug 850992.
You need to log in before you can comment on or make changes to this bug.