this post was submitted on 01 Jun 2023
7 points (100.0% liked)
Technology
37756 readers
559 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
And yet the OS you're using doesn't support it. Hmm.
Sorry, I didn't realise that these are FreeBSD-specific (I guess? I'm not too familiar with BSD)
Deployment. All web apps and APIs are moving towards containerization - Docker for smaller scale deployments, and Kubernetes for large-scale deployments.
I didn't think jails had CPU, memory, or process limits similar to what
cgroup2
provides, but it looks like this functionality was added to FreeBSD at some point. Sorry for the incorrect information.Sure, Docker has had a few issues, but overall it's more secure to run your apps in Docker containers. If an app gets compromised, the attacker will generally be stuck inside the Docker container rather than getting access to your entire system. If you're worried about (very rare) container escape security holes, using unprivileged containers helps - You can run the app inside the container as an unprivileged user, and you can also run the entire Docker container as an unprivileged user on the host system.
Security patches are easier than if you used a tar archive to install the software. With a tar archive you threw into
/opt
or whatever, the app and its config/data are often stored together, so you need to be mindful of things like not overriding customized config files. Since Dockers containers are immutable and all the actual data is stored elsewhere, it's always safe to delete the container and replace it with a patched version.It would, but Docker doesn't support it. I'm not sure how this means that the OS was worse.
They are, including its descendants (that includes the FreeBSD 4.8 fork DragonFly BSD).
How is "run this black box of arbitrary software, requiring a kernel module and numerous services" a superior deployment than
tar xf application.tgz
? Just because people do it, people could still do the wrong thing. Not every website is Facebook.No problem. I was genuinely curious.
Docker imposes additional attack vectors to the underlying system, a (for example) backdoored PHP application running inside an OpenBSD
chroot
(OpenBSD runs its built-in web server insidechroot
by default, so web applications can never reach anything outside the web folder anyway) does not, if I understand you correctly. I know that you consider the 1979 technologychroot
to be not modern, but I wonder which security feature is missing.What if nobody maintains the container anymore, although the software itself is still maintained?