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.
Selfhosted
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!
How can anyone run a Plex server on their work machine? And why doesn't their IT dept monitor their devices?
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
The shortcoming, which was discovered and reported to Plex by Tenable in March 2020, was addressed by Plex in version 1.19.3.2764 released on May 7, 2020. The current version of Plex Media Server is 1.31.1.6733.
"Unfortunately, the LastPass employee never upgraded their software to activate the patch," Plex said in a statement. "For reference, the version that addressed this exploit was roughly 75 versions ago."
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.
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.
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
Have you considered replacing the OS with proxmox and running everything in virtual machines?
I haven't. I always liked to have the possibility to use GNOME on my machine. That wouldn't work then if I were to have a Ubuntu VM, right?
And do you know if I would I get quicksync access to the i3 for transcoding ?
Thanks
Proxmox has a virtual monitor in its web interface, so you can access the desktop of a virtual machine that way. It's a little clunky but works ok for quick configuration. Alternately you could remote desktop into the virtual machine.
Quicksync is a little more tricky. GPU pass through is a pain, and I'm not sure off the top of my head about that. You can Google "proxmox quicksync passthrough" and see if any solutions will work for you. There's a chance that all you would need to do is set the processor type correctly in the virtual machine settings, but I'm not sure.
As the other reply mentioned, you can use the webui for a quick GUI in a pinch, and as for QSV, I've had more luck passing through GPUs to LXC containers, as that's what I'm doing for my Jellyfin setup with an Intel GPU in Proxmox. Link below can hopefully get you started