- #Enabling silverlight on mac with chrome 59 1080p
- #Enabling silverlight on mac with chrome 59 update
- #Enabling silverlight on mac with chrome 59 Patch
- #Enabling silverlight on mac with chrome 59 windows 10
(I only wanted to take a short clip to make a fun video out of, wasn't trying to make a pirate copy) Even using my very hardware-level screen recorder didn't seem to work effectively and locked up.
#Enabling silverlight on mac with chrome 59 windows 10
I was actually very surprised to find that trying to take a picture of a Netflix video via Print Screen on the Windows 10 Netflix app actually results in a black screen where Netflix is.
I would guess this is something to do with DRM.
#Enabling silverlight on mac with chrome 59 1080p
Why do the two MS browsers have 1080p while Chrome and FireFox are limited to 720p? Seems odd. If anyone else can get IE (11, that is, fully patched and updated) to work with Netflix without Silverlight, please share how you did it (did you ever have Silverlight installed? What did you tweak? Etc.) since some folks don't want to use anything else, and need to be better protected from crappy plug-in exploits. I did need to allow an exception through Flashblock to get it to work, so I have the feeling it's mostly from one frying pan to another, but at least one attack vector is removed entirely, and I have point by point control over the other, limiting the potential for drive-by Flash exploits. The bonus is I like the interface better (smaller thumbnails, more to see at a glance, less scrolling) and don't have to worry about Silverlight being part of my system anymore. It did insist that I enable DRM, but otherwise it's the same thing. If someone else has a different experience, maybe it's because they signed in without ever having had Silverlight.įirefox, (43+) seems to be just fine. With IE, Netflix seems to insist on Silverlight. Having read the specifications, IE should work WITHOUT Silverlight. I only ever used IE for Netflix (because it didn't work on Firefox).
I tried an experiment to find out what works. The dozen or so people who use it aren't going to be happy when they here about this.ĭoesn't Netflix still use Silverlight to some extent?Ĭan't tell what their service defaults to between HTML5 or Silverlight though.
#Enabling silverlight on mac with chrome 59 update
Everyone else should religiously update it as soon as patches become available. Readers who can browse the Internet without Silverlight are best off uninstalling it. While Silverlight vulnerabilities aren't nearly as numerous as security bugs in Adobe's Flash or Oracle's Java, Kafeine's discovery shows that the Microsoft framework has the potential to endanger a broad base of people using both Windows and OS X.
#Enabling silverlight on mac with chrome 59 Patch
It's also unclear if the Angler exploit was developed by reverse engineering the patch Microsoft released in January or if Angler developers obtained the code already available through Hacking Team. Kafeine's post doesn't specify exactly what platforms are being targeted, but Microsoft has been clear that exploits have the ability to remotely execute malicious code on both unpatched Windows and OS X devices. The vulnerability is indexed as CVE-2016-0034. The Silverlight attack was spotted earlier this week by a researcher who goes by the moniker Kafeine.
Now, exploit code for the patched vulnerability is being distributed through Angler, one of several toolkits that criminals use to seed websites with code that carry out drive-by attacks. Researchers with Russian antivirus provider Kaspersky Lab later discovered the vulnerability being exploited in the wild and privately reported it to Microsoft. As Ars reported last July, the Silverlight exploit came to light following a hack on Hacking Team's network that exposed gigabytes worth of private e-mails and other data. Further Reading How a Russian hacker made $45,000 selling a 0-day Flash exploit to Hacking TeamThe critical code-execution vulnerability, which Microsoft patched last month, was actively exploited for two years in attack code owned by Italy-based exploit broker Hacking Team.