539
After Years of Waiting Jellyfin Finally Lands on Samsung Tizen TVs (linuxiac.com)
submitted 8 months ago by to c/selfhosted@lemmy.world
88 comments fedilink hide all child comments
 

Samsung Smart TV owners can now use Jellyfin natively, as the open-source media server is now available on the Tizen platform.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 8 months ago (11 children)

It's relatively easy to restrict a smart tv to TLS/HTTPS traffic only using your router and a dns adblocker.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 11 child comments
    •
  • [–] 3 points 8 months ago (5 children)

    Its even easier to never let it on the network.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 8 months ago (4 children)

    just saying its possible

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 8 months ago* (3 children)

    You have to do a lot of work. You would have to keep up on what domains it's using (which were in the dozens four years ago for samsung), and make sure it doesn't use some as kill switches if it finds something blocked.

    We aren't stopping just ads, we are stopping spying, data sharing, snooping, network mapping, etc.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 8 months ago (2 children)

    Yeah. To be honest on the DNS side it would probably be far easier to just do a whitelist instead, block everything except your specific service. and yeah, its a stupid amount of work. i hate smart tvs but i'll be damned if im gonna pay extra for a streaming box =|

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 8 months ago (1 child)

    pretty cheap relatively speaking, and usually a lot more flexible depending on what you use.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 8 months ago

    to get something as flexible as my android tv i'd need an nvidia shield and those are going on ten years old at this point. maybe if/when they do a hardware refresh, assuming sideloading isn't completely impossible by then.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 8 months ago (4 children)

    How does it help to let the smart tv talk via encrypted channels?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 8 months ago* (3 children)

    no it helps to block everything that isnt just netflix or whatever streaming service you use. you combine a DNS adblock along with blocking all the unused ports and it severely limits the communications. you could also add a vpn to add another layer of security. idk about jellyfin but most streaming services i know use https/443 to stream to your tv. so youre only allowing the specific service you want and only on a specific port. buncha great dns blocklists here https://github.com/hagezi/dns-blocklists, and a smart tv specific one for pihole here https://github.com/Perflyst/PiHoleBlocklist/blob/master/SmartTV.txt

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 8 months ago (2 children)

    Hardcoded IPS circumvent DNS blocks.

    Restricting ports doesn't do anything since the TV isn't running a service, it is contacting one.

    Correct me if I am wrong.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 8 months ago* (last edited 8 months ago) (1 child)

    Not sure if you mean hardcoded DNS IPs or hardcoded "phone home" IPs. Hardcoded DNS addresses in devices are annoying, the only way i've found to get around that is using destination nat rules (DNAT) which requires more than a consumer router typically. hardcoded phone home IPs would get blocked by your firewall. you're right that most firewalls are set up by default to implicitly allow outbound traffic. you set up a rule that explicitly denies all outbound traffic from the TV, then only allow port 443 (or whatever port your streaming service uses) on the specific IP/IPs that your service uses. Here's Netflix's published IP info for example.

    edit also i'm fully aware it's fucking ridiculous that we as consumers have to go through this much rigamarole. you shouldnt have to be a literal network engineer to do something as simple as have an internet-connected tv that doesnt spy on you.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •