- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- selfhosted@lemmy.world
Appears to be Hetzner for now, wouldn’t be surprised if all VPS get affected eventually.
Appears to be Hetzner for now, wouldn’t be surprised if all VPS get affected eventually.
The problem is that they want to route control through their own servers for making sure you can’t use some of the extra features without paying.
A few years back they dropped some clients (including the one for my old TV) because they were dropping support for legacy SSL ciphers on their servers - and those devices didn’t have support for the new ciphers. This is a pretty stupid dependency due to the way they want to do things - so I moved to jellyfin back then, and have been encouraging people to drop plex ever since.
To be fair, old ssl isn’t really ssl at all & considered to be a vulnerability by a lot of libraries.
Without them forcing you to go through their server for user authentication it’d be a thing local to your network - where it wouldn’t really matter. Without that stupid requirement you also could just keep unsupported clients running by yourself.
But can’t you already. Just allow unencrypted clients?
But also on the other side, we’re talking about just media consumption, not banking or other sensitive data
Yeah, I agree, and ultimately shame on the tv manufacturer. However many software just won’t connect so it’s not really a plex issue. If they use a library that won’t support it…
TLS 1.0/1.1? Those were deprecated and dropped by the IETF with RFC 8996. You can’t even get a certificate using 1.0/1.1 anymore unless you are self-signing.
You can also allow unauthenticated users on certain networks, usually limited to your local nets. But I do agree that doesn’t solve the problem. I’d love to allow users to optionally use local authentication with, eg, Authelia, something built in, or an LDAP backend.