Jump to content

Search the Community

Showing results for tags 'chromecast'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 10 results

  1. Microsoft Enables Chromecast Support in Microsoft Edge Browser Microsoft has recently enabled Chromecast support in the Chromium-based Microsoft Edge browser, most likely as part a Canary update. The new version of Microsoft Edge went live as a preview earlier this year, and Microsoft is currently offering two different builds, namely Dev and Canary. The latter receives updates every day, while the Dev flavor is being updated once a week. While options to cast content have been there from the very beginning, it looks like support for the Chromecast has only recently been enabled in the browser, as noted in this reddit discussion. “For me, the "Cast..." option in the menu has been there from the launch, but haven't been functional (can't find any devices). But from today I get the cast button in the web player and Edge finds my chromecast,” the original poster explains. However, using Chromecast with Microsoft Edge was possible by enabling a dedicated flag in the browser. Learn here how to enable Chromecast in Chromium-based Microsoft Edge.Contributing to the Chromium projectWhile many think Google would force Microsoft to pull the Chromecast support from its browser, this is unlikely to happen as the software giant is becoming one of the top contributors to the Chromium project in the first place. In fact, Google itself can benefit from this collaboration, as Google Chrome could soon be improved with features that were originally available in Microsoft Edge, including its smooth scrolling system. Microsoft is expected to roll out a beta build of the new Microsoft Edge browser in the coming months, possibly at the Build developer conference next month. Additionally, the company is also working on a macOS preview build, as well as on early versions of the browser for the previous Windows editions, including Windows 7 and 8.1. No specifics have been provided as to when these could be released for download. Source
  2. How to Enable Chromecast Support in Chromium Microsoft Edge Browser If you’ve just made the switch to the new Chromium-based Microsoft Edge browser after using Google Chrome for several years, you’re obviously expecting a similar experience, especially since both browsers run on the same engine. But while Microsoft Edge is indeed based on Chromium, it doesn’t mean that all Google features and services have been migrated to the new browser. In fact, Microsoft even rolled out a list of Google goodies that got the ax, and you can read more about this here. For those making the transition, this could be an indication that Microsoft Edge lacks Chromecast support. But in fact, Chromecast support is there, only that for the time being it’s disabled because everything just seems to be a work in progress. In other words, you’ll be able to enable Chromecast support using the steps detailed below, but keep in mind that there’s a high chance that some things may not work properly and instead hit bugs or even crashes that would otherwise be fixed in a future update. Enabling Chromecast in the existing versions of Microsoft Edge, however, only comes down to turning on two different flags in the browser. To do this, you first need to launch the application (both the Dev and Canary builds work just fine) and then type the following command in the address bar: edge://flags The two flags that we are going to use in order to enable Chromecast are the following: Load Media Router Component Extension #load-media-router-component-extension Views Cast dialog - #views-cast-dialog Type their names in the search bar at the top and enable them one by one. To do this faster, you can just copy the URLs below and paste them in the Edge address bar: chrome://flags/#load-media-router-component-extension chrome://flags/#views-cast-dialog These flags are at this point set to a Default value, which means they are Disabled since they are still a work in progress. So click the drop-down menu next to each of them and switch them to Enabled. A reboot of the browser is necessary to apply the changes. In order to stream content to Chromecast devices, you then need to head over to Microsoft Edge > More tools > Cast media to device, and the Chromecast device should show up in the menu after a quick scan. On the first run, you need to grant permissions for the process in the Windows firewall. Keep in mind that this feature isn’t officially supported at this point, so there are things that could go wrong after enabling it. According to this reddit post, for example, Chromecast support in Microsoft Edge could break down Microsoft account syncing, which is a key feature of the browser right now. In other words, if you logged in with a Microsoft account and find this a key feature of the new Microsoft Edge, you better not try out this guide or revert the changes to the original configuration after applying the changes. Microsoft says it worked together with Google on making some features happen, and there’s a chance that engineers are still giving the finishing touches to Chromecast support before it becomes available for everyone. “We still have a lot to learn as we increase our use of and contributions to Chromium, but we have received great support from Chromium engineers in helping us get involved in this project, and we’re pleased to have landed some modest but meaningful contributions already. Our plan is to continue working in Chromium rather than creating a parallel project, to avoid any risk of fragmenting the community,” the Microsoft Edge team explains. Source
  3. If you use Chromecast, a Google's device to stream content to displays, e.g. to stream a video from your PC to your television, you may have noticed that Firefox is not officially supported. Google added native Chromecast support to the company's Google Chrome browser to cast content, e.g. a browser tab to a connected display. It was necessary to install a Chromecast extension in Chrome previously to do so, but that is no longer the case. Firefox users who own Chromecast devices could not integrate the device in the browser up until now; this changes with the initial release of fx_cast, an open source browser extension for Firefox that implements the Chrome Sender API in Firefox. The author of the extension released an initial version of fx_cast on GitHub. Note that it requires installation of the extension and installation of a bridge app on the operating system. The initial release brings support for Mac OS X and Linux only, a Windows binary is not provided. Firefox Chromecast support Installation is straightforward. The very first thing you may want to do is install the Firefox extension. You find it under releases on the official project website. Note: the release is listed as beta and the developer states explicitly that you should expect bugs and that site compatibility is limited at this point in time. Just click on the "xpi" file and follow the installation dialog to install the extension in Firefox. Mac OS X and Linux users find the Bridge app listed under releases as well. Windows users have the option to compile the binary from source or wait until the developer releases a Windows binary to the public. Use the new cast button in Firefox's interface once everything is set up, and the Chromecast installed properly as well. Another option that you have is to use the cast option in the context menu or the cast button that some services display natively. The interface displays the connected Chromecast devices and the cast menu to select what to cast to a device that is connected. The Firefox extension may spoof the user agent as most sites check for Chrome to determine whether to enable cast support for the connecting user. It does so for Netflix only currently, but you may add sites to the whitelist to have the user agent spoofed as well for connections to these sites. The variable <all_urls> adds all sites to the whitelist. The settings displays a good range of options already. You may change the HTTP server port, enable screen mirroring, or change receiver options in regards to media casting. Closing Words The extension is in its early stages of development but it works surprisingly well on some sites. Most users may want to wait until the developer releases a stable build (and Windows binary) before they give it a try though. Source: fx_cast brings Chromecast streaming to Firefox (early look) (gHacks - Martin Brinkmann)
  4. Hackers have hijacked thousands of exposed Chromecast streaming devices to warn users of the latest security flaw to affect the device. But other security researchers say that the bug — if left unfixed — could be used for more disruptive attacks. The culprits, known as Hacker Giraffe and J3ws3r, have become the latest person to figure out how to trick Google’s media streamer into playing any YouTube video they want — including videos that are custom-made. This time around, the hackers hijacked forced the affected Chromecasts to display a pop-up notice that’s viewable on the connected TV, warning the user that their misconfigured router is exposing their Chromecast and smart TV to hackers like themselves. Not one to waste an opportunity, the hackers also asks that you subscribe to PewDiePie, an awful internet person with a popular YouTube following. (He’s the same hacker who tricked thousands of exposed printers into printing support for PewDiePie.) The bug, dubbed CastHack, exploits a weakness in both Chromecast and the router it connects to. Some home routers have enabled Universal Plug and Play (UPnP), a networking standard that can be exploited in many ways. UPnP forwards ports from the internal network to the internet, making Chromecasts and other devices viewable and accessible from anywhere on the internet. As the two say, disabling UPnP should fix the problem. “We have received reports from users who have had an unauthorized video played on their TVs via a Chromecast device,” a Google spokesperson told TechCrunch. “This is not an issue with Chromecast specifically, but is rather the result of router settings that make smart devices, including Chromecast, publicly reachable,” the spokesperson said. That’s true on one hand, but it doesn’t address the underlying issue — that the Chromecast can be tricked into allowing an unauthenticated attacker the ability to hijack a media stream and display whatever they want. Bishop Fox, a security consultancy firm, first found a hijack bug in 2014, not long after the Chromecast debuted. The researchers found that they could conduct a “deauth” attack that disconnects the Chromecast from the Wi-Fi network it was connected to, causing it to revert back to its out-of-the-box state, waiting for a device to tell it where to connect and what to stream. That’s when it can be hijacked and forced to stream whatever the hijacker wants. All of this can be done in an instant — as they did — with a touch of a button on a custom-built handheld remote. Two years later, U.K. cybersecurity firm Pen Test Partners discovered that the Chromecast was still vulnerable to “deauth” attacks, making it easy to play content on a neighbor’s Chromecasts in just a few minutes. Ken Munro, who founded Pen Test Partners, says there’s “no surprise that somebody else stumbled on to it,” given both Bishop Fix found it in 2014 and his company tested it in 2016. “In fairness, we never thought that the service would be exposed on the public internet, so that is a very valid finding of his, full credit to him for that,” Munro told TechCrunch. (Google said in a follow-up email that it’s working to fix the deauth bug.) He said the way the attack is conducted is different, but the method of exploitation is the same. CastHack can be exploited over the internet, while Bishop Fox and his “deauth” attacks can be carried out within range of the Wi-Fi network — yet, both attacks let the hacker control what’s displayed on the TV from the Chromecast, he said. Munro said Google should have fixed its bug in 2014 when it first had the chance. “Allowing control over a local network without authentication is a really silly idea on [Google’s] part,” he said. “Because users do silly things, like expose their TVs on the internet, and hackers find bugs in services that can be exploited.” But Munro said that these kinds of attacks — although obnoxious and intrusive on the face of it — could be exploited to have far more malicious consequences. In a blog post Wednesday, Munro said it was easy to exploit other smart home devices — like an Amazon Echo — by hijacking a Chromecast and forcing it to play commands that are loud enough to be picked up by its microphone. That’s happened before, when smart assistants get confused when they overhear words on the television or radio, and suddenly and without warning purchase itemsfrom Amazon. (You can and should turn on a PIN for ordering through Amazon.) To name a few, Munro said it’s possible to force a Chromecast into loading a YouTube video created by an attacker to trick an Echo to: “Alexa, order an iPad,” or, “Alexa, turn off the house alarm,” or, “Alexa, set an alarm every day at 3am.” Amazon Echos and other smart devices are widely considered to be secure, even if they’re prone to overhearing things they shouldn’t. Often, the weakest link are humans. Second to that, it’s the other devices around smart home assistants that pose the biggest risk, said Munro in his blog post. That was demonstrated recently when Canadian security researcher Render Man showed how using a sound transducer against a window can trick a nearby Amazon Echo into unlocking a network-connected smart lock on the front door of a house. “Google needs to properly fix the Chromecast deauth bug that allows casting of YouTube traffic,” said Munro. Source
  5. Google in the coming weeks is expected to fix a location privacy leak in two of its most popular consumer products. New research shows that Web sites can run a simple script in the background that collects precise location data on people who have a Google Home or Chromecast device installed anywhere on their local network. Craig Young, a researcher with security firm Tripwire, said he discovered an authentication weakness that leaks incredibly accurate location information about users of both the smart speaker and home assistant Google Home, and Chromecast, a small electronic device that makes it simple to stream TV shows, movies and games to a digital television or monitor. Young said the attack works by asking the Google device for a list of nearby wireless networks and then sending that list to Google’s geolocation lookup services. “An attacker can be completely remote as long as they can get the victim to open a link while connected to the same Wi-Fi or wired network as a Google Chromecast or Home device,” Young told KrebsOnSecurity. “The only real limitation is that the link needs to remain open for about a minute before the attacker has a location. The attack content could be contained within malicious advertisements or even a tweet.” It is common for Web sites to keep a record of the numeric Internet Protocol (IP) address of all visitors, and those addresses can be used in combination with online geolocation tools to glean information about each visitor’s hometown or region. But this type of location information is often quite imprecise. In many cases, IP geolocation offers only a general idea of where the IP address may be based geographically. This is typically not the case with Google’s geolocation data, which includes comprehensive maps of wireless network names around the world, linking each individual Wi-Fi network to a corresponding physical location. Armed with this data, Google can very often determine a user’s location to within a few feet (particularly in densely populated areas), by triangulating the user between several nearby mapped Wi-Fi access points. [Side note: Anyone who’d like to see this in action need only to turn off location data and remove the SIM card from a smart phone and see how well navigation apps like Google’s Waze can still figure out where you are]. “The difference between this and a basic IP geolocation is the level of precision,” Young said. “For example, if I geolocate my IP address right now, I get a location that is roughly 2 miles from my current location at work. For my home Internet connection, the IP geolocation is only accurate to about 3 miles. With my attack demo however, I’ve been consistently getting locations within about 10 meters of the device.” Young said a demo he created (a video of which is below) is accurate enough that he can tell roughly how far apart his device in the kitchen is from another device in the basement. “I’ve only tested this in three environments so far, but in each case the location corresponds to the right street address,” Young said. “The Wi-Fi based geolocation works by triangulating a position based on signal strengths to Wi-Fi access points with known locations based on reporting from people’s phones.” Beyond leaking a Chromecast or Google Home user’s precise geographic location, this bug could help scammers make phishing and extortion attacks appear more realistic. Common scams like fake FBI or IRS warnings or threats to release compromising photos or expose some secret to friends and family could abuse Google’s location data to lend credibility to the fake warnings, Young notes. “The implications of this are quite broad including the possibility for more effective blackmail or extortion campaigns,” he said. “Threats to release compromising photos or expose some secret to friends and family could use this to lend credibility to the warnings and increase their odds of success.” When Young first reached out to Google in May about his findings, the company replied by closing his bug report with a “Status: Won’t Fix (Intended Behavior)” message. But after being contacted by KrebsOnSecurity, Google changed its tune, saying it planned to ship an update to address the privacy leak in both devices. Currently, that update is slated to be released in mid-July 2018. According to Tripwire, the location data leak stems from poor authentication by Google Home and Chromecast devices, which rarely require authentication for connections received on a local network. “We must assume that any data accessible on the local network without credentials is also accessible to hostile adversaries,” Young wrote in a blog post about his findings. “This means that all requests must be authenticated and all unauthenticated responses should be as generic as possible. Until we reach that point, consumers should separate their devices as best as is possible and be mindful of what web sites or apps are loaded while on the same network as their connected gadgets.” Earlier this year, KrebsOnSecurity posted some basic rules for securing your various “Internet of Things” (IoT) devices. That primer lacked one piece of advice that is a bit more technical but which can help mitigate security or privacy issues that come with using IoT systems: Creating your own “Intranet of Things,” by segregating IoT devices from the rest of your local network so that they reside on a completely different network from the devices you use to browse the Internet and store files. “A much easier solution is to add another router on the network specifically for connected devices,” Young wrote. “By connecting the WAN port of the new router to an open LAN port on the existing router, attacker code running on the main network will not have a path to abuse those connected devices. Although this does not by default prevent attacks from the IoT devices to the main network, it is likely that most naïve attacks would fail to even recognize that there is another network to attack.” For more on setting up a multi-router solution to mitigating threats from IoT devices, check out this in-depth post on the subject from security researcher and blogger Steve Gibson. Source
  6. No matter which service you prefer to use to watch the latest and greatest television series, one of the last things you may fancy doing is to sit through the same intro again and again. For instance, if you decide to watch a season of the now-rescued Brooklyn Nine-Nine, you would you spend a bit over seven minutes in total just watching the intro play at the beginning of each episode. Of course, some people may not mind that while others may think it may be a case of #firstworldproblems but being able to easily skip the intro has been a welcome timesaver for Netflix customers for some time. Unfortunately, if you've been using a Chromecast device, this has not been the case but now that shortcoming appears to have been fixed. In the latest version of the Netflix app for Android, v6.3.0, the option to immediately skip the intro will appear at the bottom of the screen, making it super easy to get on with the important task of re-immersing yourself in your favorite content. At the time of writing, Netflix has not yet updated its help page to make specific mention of the Chromecast supporting the skip intro feature. However, its formal inclusion may still be waiting on iOS picking up the capability when connected to a Chromecast device. More details source < Clic here >
  7. Chrome no longer needs an extension to beam media to your TV. The Google Cast integration in Chrome. Google Cast—the protocol that powers Chromecast—previously worked inside of Chrome thanks to an extension released by Google. Buttons on YouTube, Google Music, and other sites allowed you to beam music and video to your TV or stereo system. Now you no longer need an extension to sling media across the room. Google has built the protocol directly into Chrome. Like all Chrome features, Cast support started in the "Dev" and "Beta" versions. Cast has finally hit the stable channel that most consumers use. The Cast buttons in web site UIs will continue to work the way they always have, and if you click on the Chrome menu button, you'll be treated to a new "Cast..." option that can beam an entire tab to your television. To get the new Cast functionality, you just need the latest version of Chrome and a Cast-aware device on your local network. According to this page, the old Cast extension will apparently still live on for those who want the tab-beam button in their toolbar. Article source
  8. The Popcorn Time app brought BitTorrent streaming to the masses and despite early setbacks the "Netflix for pirates" appears to be here to stay. One of the most popular Popcorn Time forks currently has millions of users and is downloaded tens of thousands of time a day. The Popcorn Time phenomenon took the Internet by storm earlier this year. The software became the subject of hundreds of news articles by offering P2P streaming in an easy to use Netflix-style interface. Overwhelmed by the response and the legal pressure that came with it the original team quickly retired. However, since the code is open source, many competing forks quickly adopted the project, each taking it in a different direction. The storm calmed down somewhat after a few months, but it appears that the “Netflix for pirates” idea is here to stay. TorrentFreak reached out to one of the most popular Popcorn Time forks at time4popcorn.eu to find out how they are faring. While the developers are hesitant to reveal any hard data about their software’s popularity, they note that they have acquired millions of users over the past several months. On an average day tens of thousands of people download the application, with Sunday being the most popular day by far. The developers further reveal that roughly half of all Popcorn Time downloads are for the Windows platform. The Mac version is in second place with 25%, followed by Android and Linux with 20% and 5% respectively. For the developers this popularity is one of the main reasons to continue innovating through new features. For example, last month they integrated a free VPN so users can hide their IP-address from the rest of the world. “The million of users are the wind in our sails. We tell this to them all the time – they are the reason we’re putting in all the hard we’ve been putting in for the past 3.5 months,” the Time4Popcorn team tells TorrentFreak. “In none of our previous projects did we experience this kind of ‘madness’. This is really what keeps us working around the clock on this project,” they add. This week the Popcorn Time variant released another highly anticipated feature in their latest Alpha release, support for Chromecast. This means that users can now stream films directly to Chromecast with just a simple click. Chromecast support was one of the most requested Popcorn Time features, the developers told us. It’s also directly in line with one of the main goals of the software, which is creating an optimal viewing experience. “The first goal for Popcorn Time is to make the best viewing experience for all our users, and the other is to make the safest watching experience so all our users can fulfill the first goal without getting in trouble,” the Time4Popcorn team says. While Chromecast support is a milestone, the developers mention that there is more exiting news ahead in the not too distant future. “This week’s Alpha release with Chromecast support is nothing compared to what we have coming,” we were told. Stay tuned… Source: TorrentFreak
  9. By Seth Rosenblatt February 3, 2014 10:00 AM PST Google throws open the development doors to Chromecast so that app makers can get their apps on your TV. Mario Queiroz, vice president of product management for Chromecast, demonstrates switching Chromecast media controls in Netflix from one device to another at Google HQ. Google hopes developers will flock to the new Chromecast SDK. (redit: Seth Rosenblatt/CNET) A key part of Google's plans to build the future of its Chromecast dongle has slipped into place as the company unlocked its Chromecast software development kit on Monday morning. The Google Cast Software Development Kit (SDK), available now, will allow app developers to give their users the option to stream their apps or Web sites to the Chromecast, which acts like a receiver that you plug into your TV's HDMI port. Web site compatibility only works in Google Chrome via extension, also available today. The Cast SDK has been available previously only in restricted form, with Google working with well-known companies such as HBO, Pandora, and Netflix to prove the device's worth. Now that it's open to all, developers will be able to register devices and apps for testing and publishing. Once the Cast SDK has been integrated with an app, current users can get the updated app through their regular app marketplace. Chromecast's future depends on developers making their apps compatible with the device. "With the Chromecast, we're resetting consumer applications," said Rishi Chandra, Chromecast's director of product management. People, he said, "should expect their phones or tablet applications to just work on the television." That's a major change for people on both the development and user ends of the app. If the Chromecast's upward trajectory continues, you can bet it will play a big role in Google's desire to get on all your screens. Chromecast's limited development has thus far demonstrated only a small part of its potential, tapping into video, music, and local media applications like RealPlayer Cloud. Its future, said Chandra, depends on developers. The new Chromecast SDK will allow more kinds of apps to show up on your TV, including locally stored files and games. (Credit: CNET) "Gaming is an exciting opportunity for what you can do with Chromecast," he said, as one example of an area where developers could spend more time. "It's exactly the right model. The fact that it works with your iOS phone and Android tablet and Windows laptop is true multiscreen. There's a lot of potential there," he said. As simple as the Chromecast is, making sure that it was easy to develop for took some time. One thing Google learned, said Chandra, is that Chromecast developers are like Chromecast consumers: they want it to just work. When it comes to the SDK, he said that "developers don't really need or want all the features. They want turnkey solutions." When it comes to all things Chromecast, the geniuses at Google may have finally learned their lesson: keep it simple, stupid. Updated at 1:57 p.m. PT: to specify the RealPlayer app as RealPlayer Cloud. Corrected at 11:15 a.m.: to change the day that Google made its announcement to Monday, February 3. http://news.cnet.com/8301-1023_3-57617969-93/google-opens-chromecast-to-all-developers
  10. Google isn't giving up its living room ambitions. The company is said to be working on a "Nexus TV" device that will run Android, stream video from services like Netflix, Hulu, and YouTube, and play a selection of video games. The rumor comes from The Information's Amir Efrati, who cites an anonymous Google employee. The device is said to be ready for launch as soon as the first half of next year, according to the report. Rumors of a Google-made Android set top box go back to July of this year, when The Wall Street Journal reported that such a device was demoed by Andy Rubin behind closed doors at the 2013 Consumer Electronics Show in Las Vegas. Sources told the paper at the time that the box included a Kinect-like motion sensor and could be controlled with an Android smartphone. Today's report from The Information corroborates these details (though a motion sensor is not mentioned), and adds that a purpose-built touchpad remote could be included with the set-top box. Google reportedly showed off a version of the box to developers as recently as this fall. It's said that the device will not support live broadcast, which would mean Google could avoid the hassle of trying to bring traditional content providers on board. That's a task that's so far proved impossible for other companies: Intel abandoned its efforts to launch an internet set-top box after failing to secure such deals, and it's rumored that an Apple television device has been delayed for similar reasons. If the Nexus TV reports are accurate, Google seems to be pursuing a similar strategy as Amazon, which is rumored to have a set-top box of its own set for next year. Google has launched a number of products to attempt to gain a foothold in the living room, starting with the ill-fated (but still living) Google TV operating system that manufacturers built into smart TVs and other devices. It later announced the expensive Nexus Q (which never officially went on sale), and this year it began selling a small HDMI dongle called the Chromecast, which streams from just a few services and costs $35. The latter has seen some success, but it's a device with a simple feature set. A fully-fledged Nexus TV set-top box that runs Android would be in a different category — though today's report suggests it will be "aggressively priced." Source
  • Create New...