hamielis randean neelsan
Hasan Fogg
I am having an issue with playing Netflix content through Safari since upgrading to Yosemite. Specifically, Netflix will start to play the content and then display an error after a few seconds. The error reads "Whoops, something went wrong... display error. There appears to be a display problem. Please ensure your monitor is HDCP compliant and is not mirror using airplay."
My monitor is HDCP compliant (HP ZR30W) and it's the only monitor connected to my 2014 MacPro. I presume this is an issue with the latest version of Safari and all the next extensions Apple added to support Netflix streaming without the Silverlight plugin.
What has changed all of a sudden that we get these HDCP errors. I was watching Starttrek discovery when suddenly after about 5/10 minutes of play it stopped and gave me this error. This must be a bug in Safari / OSX and or Netflix. I never had any problems before today using netflix on my mac.
The problem still persists with MacOS 10.13.2 and Safari 11.02. I suspect that Apple is not interested in fixing the problem: too busy selling iPhones. I've had no problems with Chrome and Netflix. Maybe Apple will realize that first you switch to Chrome then to the Pixel phone then to those (relatively cheap) powerful Windows machines.
Carolyn - My Silverlight plug-in was already properly configured. With Yosemite & Safari 8.0, Netflix no longer uses Silverlight. Instead, it plays content using HTML5. So, the plugin should not be the issue.
Actually, I posted the same question a few days ago, this is how I fixed it: Enter Netflix and go to your account, then to your profile, then to Playback settings and there, uncheck the bottom option (prefer HTML5 instead of Silverlight), you should be able to play movies again... obviously, you have to have Silverlight in your computer.
I'm running into this same problem. I also recently installed Yosemite. For me though, it stopped working when I updated my Adobe Flash plugin today. Although, I'm not sure that should be related. Switching my netflix preference to Silverlight, as was suggested above, worked and now I can play netflix again. But This seems like it should be unnecessary.
Unplugging the second monitor from the thunderbolt-VGA adaptor fixed the issue, and now Netflix plays with the HTML5 setting turned on! So it would appear that the second monitor was the problem. Which would track with what this page says:
The page states that a Thunderbolt-DVI connector should work. Luckily this monitor has both, so the next thing I will try is to buy a Thunderbolt-DVI adaptor and retest with both monitors attached (I don't have one at the moment). If that works, I'll post the results, maybe next week.
This kind of stinks because I've always been two-monitor dude, I like having a movie playing on one monitor while I work on the other for example. For now, until I get the adaptor, I'll switch netflix back to using silverlight, which seems to still work with both monitors attached.
This issue only occurs on my desktop MacPro. I also own a MacBook Pro. If I change the Netflix HTML5 settings, then my MacBook Pro will lose the benefit of HTML5 and longer battery life. Of course it doesn't matter too much for the desktop MacPro.
My monitor is HDCP compliant as well and I only have one connected. It's connected by a third-party Thunderbolt-to-DisplayPort adapter (not mini-displayport). Maybe I should try the HDMI and see if it works, although I hate HDMI. Thanks for the idea!
While this workaround may work, you should not be forced to use one sort of monitor or another with a computer that you own. If you google HDCP, you'll see that it's been broken since before it was actually released and therefore serves no purpose other than to annoy and antagonize legitimate users. It is totally unacceptable to me that Apple is doubling down on this technology with Yosemite/HTML5. I have an old projector that still works great with DVI but does not support HDCP. That means I can't watch iTunes videos, and now apparently can't watch HTML5 videos. I am certainly not about to replace working technology because of a software problem. What a waste.
Dyn, a New Hampshire-based company that monitors and routes Internet traffic, was the victim of a massive attack that began at 7:10 a.m. ET Friday morning. The issue kept some users on the East Coast from accessing Twitter, Spotify, Netflix, Amazon, Tumblr, Reddit, PayPal and other sites.
Troubling to security experts was that the attackers relied on Mirai, an easy-to-use program that allows even unskilled hackers to take over online devices and use them to launch DDoS attacks. The software uses malware from phishing emails to first infect a computer or home network, then spreads to everything on it, taking over DVRs, cable set-top boxes, routers and even Internet-connected cameras used by stores and businesses for surveillance.
The source code for Mirai was released on the so-called dark web, sites that operate as a sort of online underground for hackers, at the beginning of the month. The release led some security experts to suggest it would soon be widely used by hackers. That appears to have happened in this case.
The attack comes at a time of heightened public sensitivity and concern that the nation's institutions and infrastructure could face large-scale hacking attacks. The most recent example has been the release of emails stolen from the servers of the Democratic National Committee, which U.S. intelligence sources say was the work of Russia. The topic has come up frequently during the fall's hard-fought presidential campaign.
A post on Hacker News first identified the attack and named the sites that were affected. Several sites, including Spotify and GitHub, took to Twitter Friday morning to post status updates once the social network was back online.
Twitter users similarly took to the service to keep lists of which sites were down and comment on the situation. The term DDoS quickly vaulted to among the top of the site's list of "Trending Topics" in the United States.
As part of its business, Dyn provides DNS services for a given swath of the Internet, effectively its address book. DNS stands for Domain Name System, the decentralized network of files that link the domain names human beings use, such as usatoday.com, with their numeric Internet Protocol addresses, such as 184.50.238.11, which is how computers look for websites.
The attack hit the Dyn server that contains that address book, a service Dyn provides to multiple Internet companies. For anyone attempting to link to a site that used the Dyn service, when they entered an address such as twitter.com or tumblr.com it was unable to link them to the proper numerical IP address, so to their computer it appeared the site was unavailable.
"If you take out one of these DNS service providers, you can disrupt a large number of popular online services, which is exactly what we're seeing today," said Jeremiah Grossman, chief of security strategy at cybersecurity startup SentinelOne.
"We've never really seen anything this targeted [that] impacts so many sites," said David Jones, director of sales engineering at software IT company Dynatrace. "Typically DDoS attacks are targeted at individual sites. DNS is like a phone book: this is like someone is attacking the phone company and burning all the phone books at the same time."
A senior government official told CNN that the DDoS attacks "mainly have resulted only in the slowing down of internet access to various websites on the East Coast." The official believes these attacks were very crude attempts.
Amazon Web Services was also experiencing connectivity issues on Friday around the same time as the Dyn attacks. AWS is used by more than 1 million companies, including GE (GE), News Corp (NWS). and Capital One (COF).
"These [DDoS attacks] take the form of precisely calibrated attacks designed to determine exactly how well these companies can defend themselves, and what would be required to take them down," wrote security technologist Bruce Schneier in a blog post last month.
Most stock quote data provided by BATS. Market indices are shown in real time, except for the DJIA, which is delayed by two minutes. All times are ET. Disclaimer. Morningstar: 2019 Morningstar, Inc. All Rights Reserved. Factset: FactSet Research Systems Inc.2019. All rights reserved. Chicago Mercantile Association: Certain market data is the property of Chicago Mercantile Exchange Inc. and its licensors. All rights reserved. Dow Jones: The Dow Jones branded indices are proprietary to and are calculated, distributed and marketed by DJI Opco, a subsidiary of S&P Dow Jones Indices LLC and have been licensed for use to S&P Opco, LLC and CNN. Standard & Poor's and S&P are registered trademarks of Standard & Poor's Financial Services LLC and Dow Jones is a registered trademark of Dow Jones Trademark Holdings LLC. All content of the Dow Jones branded indices S&P Dow Jones Indices LLC 2019 and/or its affiliates.
On October 21, 2016, three consecutive distributed denial-of-service attacks were launched against the Domain Name System (DNS) provider Dyn. The attack caused major Internet platforms and services to be unavailable to large swathes of users in Europe and North America.[3][4] The groups Anonymous and New World Hackers claimed responsibility for the attack, but scant evidence was provided.[5]
The US Department of Homeland Security started an investigation into the attacks, according to a White House source.[30][31][32] No group of hackers claimed responsibility during or in the immediate aftermath of the attack.[33] Dyn's chief strategist said in an interview that the assaults on the company's servers were very complex and unlike everyday DDoS attacks.[34] Barbara Simons, a member of the advisory board of the United States Election Assistance Commission, said such attacks could affect electronic voting for overseas military or civilians.[34]
Dyn disclosed that, according to business risk intelligence firm FlashPoint and Akamai Technologies, the attack was a botnet coordinated through numerous Internet of Things-enabled (IoT) devices, including cameras, residential gateways, and baby monitors, that had been infected with Mirai malware. The attribution of the attack to the Mirai botnet had been previously reported by BackConnect Inc., another security firm.[35] Dyn stated that they were receiving malicious requests from tens of millions of IP addresses.[6][36] Mirai is designed to brute-force the security on an IoT device, allowing it to be controlled remotely.
90f70e40cf