node-castv2

I had success a couple of years ago patching the Chrome binary to put my own CA Chromecast roots in there and then broadcasting my software device over mdns [0]. At that time the newer protocol wasn't implemented in Chrome yet so the furthest I got was appearing in the device list. But now it is implemented [1], so maybe I should revisit. Of course this isn't a general solution since it requires patching the binary instead of having some other way to use custom keys (they compile them into Chrome today, and of course other devices are even more closed). 0 - https://github.com/thibauts/node-castv2/issues/2#issuecommen... 1 - https://bugs.chromium.org/p/chromium/issues/detail?id=809249

If you want to do the same for Chromecast it's not possible yet. Google seems to have locked down their API. There is some open-source projects that are trying to reverse engineer it but the problem seems to be linked to crypto keys used to authenticate real Chromecast devices: https://github.com/thibauts/node-castv2/issues/2

AFAIK it is actually using a proprietary streaming protocol called CASTv2. It has been a community effort to reverse engineer the protocol and write implementations. Some useful links: https://github.com/vincentbernat/nodecastor // one of the earliest attempts of figuring out CASTv2 https://github.com/thibauts/node-castv2 // one of the first libraries to support chromecast streaming based on the works of vincentbernat.

you and me man but the client verifies the server has a certificate at least according to https://github.com/thibauts/node-castv2

The Chromecast protocol specification (CASTV2) itself is sort of open. To implement it on macOS I did a little bit of reverse engineering and used a description of the protocol I found here: https://github.com/thibauts/node-castv2

There's also a fascinating (in my opinion) write-up on the wire protocol, which was presumably reverse-engineered for this library: https://github.com/thibauts/node-castv2#protocol-description

Yeah, except for the fact that Chromecast sender apps perform a cert check now, so open implementations don't work. https://github.com/thibauts/node-castv2/issues/2

These links might be of some help : https://github.com/thibauts/node-castv2#protocol-description https://github.com/thibauts/node-castv2-client

One thing it may allow is grabbing the private key it uses for Device Authentication and emulate a Chromecast on other devices. It would enable streaming from Chrome to anything using the Chromecast protocol. See [1]. I had a go at implementing the protocol server-side on node, so it's basically waiting for a valid cert. I couldn't test it much though it should work. See [2] and [3]. Any help welcome. [1] https://github.com/thibauts/node-castv2/issues/2 [2] https://github.com/thibauts/node-castv2 [3] https://github.com/thibauts/node-castv2/blob/master/lib/serv...

You might be interested in these https://github.com/thibauts/node-castv2 https://github.com/thibauts/node-castv2-client