🇮🇹 🇪🇪 🖥

  • 0 Posts
  • 63 Comments
Joined 1 year ago
cake
Cake day: March 19th, 2024

help-circle


  • I presume you mean running Plex in host namespace. I don’t do that as I run the synology package, but I can totally see the issue you mean.

    Running in host namespace is bad, not terrible, especially because my NAS in on a separate VLAN, so besides being able to reach other NAS local services, cannot do do much. Much much much less risk than exposing the service on the internet (which I also don’t).

    Also, this all is not a problem for me, I don’t use remote streaming at all, hence why I am also experimenting with jellyfin. If I were though, I would have only 2 options: expose jellyfin on the internet, maybe with some hacky IP whitelist, or expect my mom to understand VPNs for her TV.

    (which doesn’t harden security as much as you think)

    Would be nice to elaborate this. I think it reduces a lot of risk, compared to exposing the service publicly. Any vulnerability of the software can’t be directly exploited because the Plex server is not reachable, you need an intermediate point of compromise. Maybe Plex infra can be exploited, but that’s a massively different type of attack compared to the opportunities and no-cost “run shodab to check exposed Plex instances” attack.



  • Well, as an application it has a huge attack surface, it’s also able to download stuff from internet (e.g., subs) and many people run it on NAS. I run jellyfin in docker, I didn’t do a security assessment yet, but for sure it needs volume mounts, not sure about what capabilities it runs with (surely NET_BIND, and I think DAC_READ_SEARCH to avoid file ownership issues with downloaders?). Either way, I would never expose a service like that on the internet.


  • Not to be “achtuallying” bit VPN is not a way to remote stream, it’s a way to bring remote clients in the local network.

    Likewise exposing services on the internet…not really going to happen esepcially for people - like me - that run plex/jellyfin on their NAS.

    I don’t have a horse in this race, i don’t use remote streaming, I only ever streamed from my nas to my 2 TVs, and I am experimenting with jellyfin. But for those who do need remote streaming, jellyfin is going to be problematic.






  • Jamf doesn’t do anything for this problem, besides costing you a fortune in both license and maintenance/operation. Especially if you are not a Mac shop.

    MDM at most can be used as a reactive tool to do something on the machine - as long as the one with the machine in their hand leaves the network connection on.

    There are much cheaper solution to do that for 1 machine, and -as others correctly pointed out- the only solution (partial) here is not storing the data on a machine you don’t control. Period.









  • I am not a fan of some of his ideas either, especially the ones tending towards libertarianism. Some other ideas instead are quite decent, like how he thinks companies should give back to the community. He also built a tech company without VC funding and with a good share of ownership for workers (which I think is nice), without any marketing (which I despise as industry) and generally without the predatory nature that 98% of tech companies have nowadays.

    I am sure you are referring to the Brave debacle of months back, and FWIW, I agree with his position on that particular issue. Anyway, considering that I have no ideas about the positions for the CEOs/founders of the alternatives, I think it’s still a very worthy compromise to have a good product (incl. nonfunctional qualities like privacy, ecological impact etc.).