- cross-posted to:
- technology@lemmy.ml
- cross-posted to:
- technology@lemmy.ml
cross-posted from: https://lemmy.ca/post/40385572
If you’re getting “Untrusted device” on your Chromecast today, you’re not alone. It looks like an expired cert.
Hopefully, the company can send out a server-side fix in short order.
The Chromecast (2nd gen) and Chromecast Audio are two of Google’s oldest devices, with both announced at the same event in September of 2015.
Yeah those are likely considered dead and abandoned by google, they will probably not give a shit about it.
I have to think there’s some project out there where you could plug a 3.5 to RCA adapter into a Pi and use it in a similar fashion. Maybe would need a bridge app from the ‘cast’ function to connect to it, but I expect not impossible.
I bought a Chromecast Audio right before they were discontinued, trying to get in while I still could. It’s the only way I cast to a wired speaker system from the 80s that works reliably.
I loved the convenience but I will not go along with their cash grabs. I will not buy their new product because they took away the old one that was still working.
They were discontinued because they lost a patent case. This one I won’t blame on Google… cept maybe for their legal team not flagging it for patent infringement.
There’s nothing else like the Chromecast audio, and it’s a crying shame that Google discontinued them. I have four and rely on them every day. I sure hope they will fix this issue.
Those certificates should not exist in first place. That is just a bad design.
You think that traffic should be unencrypted?
It’s possible to encrypt traffic without a cert that expires.
I don’t know much about how Chromecast works but my bet is that it’s like a hacked together lighthttp or nginx server, which is why it needs a SSL cert renewal.
If I remember correctly I have seen an nginx page in combination with some chromecast device.
I have been affected… Glad I saw this, at least I know it’s not just me.