16
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Aug 2023
16 points (94.4% liked)
Selfhosted
40113 readers
331 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
You are not being overly cautious. You should absolutely practice isolation. The LastPass hack happened because one of their engineers had a vulnerable Plex server hosted from his work machine. Honestly, next iteration of my home network is going to probably have 4 segments. Home/Users, IOT, Lab, and Work.
interesting, even if they got access to the plex service, how they could have escaped the plex docker container?
i run pretty much the same stack as OP, but also run immich and paperless. i very much care if someone else have a way to access those...
They weren't using docker and the Plex software was multiple years out of data:
https://thehackernews.com/2023/03/lastpass-hack-engineers-failure-to.html
In the LastPass case, I believe it was a native Plex install with a remote code execution vulnerability. But still, even in a Linux container environment, I would not trust them for security isolation. Ultimately, they all share the same kernel. One misconfiguration on the container or an errant privilege escalation exploit and you're in.
It wasnt containerized sadly but remember in a container you still share (albeit split by cgroups) kernel space and the kernel. Only userland is isolated.
So kernel level sploits are still a concern. Wasn't the case here but still.
Thanks. I mean I probably don't have that threat level, but you are right - it also feels good to have isolation.
The downside was the cost of the 2nd machine (~400$) and running it (~5$/month) and the time involved.
But I tend toward thinking it is the right choice
How can anyone run a Plex server on their work machine? And why doesn't their IT dept monitor their devices?