- #Microsoft silverlight for mac saying that it's not installed when it is install#
- #Microsoft silverlight for mac saying that it's not installed when it is update#
- #Microsoft silverlight for mac saying that it's not installed when it is code#
I guess it's too much trouble for MS to keep things "linked" or otherwise tied together, so that it knows "ignore X update" means Y should be ignored as well. I'm not sure why re-appearing hidden items is a problem.
#Microsoft silverlight for mac saying that it's not installed when it is update#
The incessant recurrence in the update center. They figure both devs and users alike are better off if they push it on users until it is totally phased out. It's in the wild and not going away for some time now. I can understand pushing the deprecated framework. It's not really a great problem for me, but I find it odd that this installation of Windows Update continues to push it, despite the deprecation and recognised risk of installing it. I've been aware that it's a POC for many years and never loaded it onto this box at all. Yet even when hidden by me it continues to appear the next time I run MS Update despite the fact that even MS says to not use it anymore. The download appears as an optional update in Win7 MS Updates and is for the Silverlight installation, not an update for an already existing installation. I never did and have checked several times to see if it can be found on my system.
#Microsoft silverlight for mac saying that it's not installed when it is code#
Side-side-note: seriously Flash, 714 total vulnerabilities? 22 critical ones, 21 of them code execution ones with severity score 10 this year alone? smh I'm not sure that's a crown anyone wants, though, given the competition.
#Microsoft silverlight for mac saying that it's not installed when it is install#
Java especially is problematic, since it's also used for system installed JARs/software packages but likes to try to install browser extensions at the same time.Īs a side note, Silverlight has at least had a better run of things when it comes to exploits than either Flash or Java. Ultimately, HTML5 APIs are making these more and more obsolete, but that doesn't help when you actually need to use a particular application designed in one of them and there is no other alternative to replace it. It's more important, as an end user, to be in total control of when they actually run. It's easy to say "don't ever install them or let them install" but honestly shit happens, and one way or another these usually end up on a given system. Your browser running these simply because a page requests it is really the issue you need to be the most concerned about, because none of these will ever be 100% secure, and eventually you'll come across something that only works with one of them installed. Yeah I feel like that's "unfair," and no, I'm not at all saying users are to blame, but at this point if you have silverlight, flash, java, or anything else that's an executable plugin/extension just running whenever a page requests it, you are going to eventually get hit with a total system pwning 0day from something that goes beyond the browser sandbox. (as far as I'm aware, all of the browsers now allow this: the only difference is whether you have to individually blacklist each plugin to be click to play, sometimes with warnings that updates can flip it back to not blacklisted, or whether you universally blacklist them all and then can manage exceptions) Make sure all of your executable extensions are set to right click to run. Don't run browsers that can't make all system executable plugins/extensions be universally right-click-to-run.
0 kommentar(er)
