Cubic VS runc

I've used Cubic before and really liked it.

Do you have any resource, tip or suggestion to proper debloat it? I'm also try to find out how https://github.com/PJ-Singh-001/Cubic works to make a custom ISO.

> a full OS made on web technologies

I think that's not unlike what ChromeOS is trying to be? With the APIs like WebSerial and WebUSB enabling web apps to do the same things native apps could for years now. (Of course, you can use these in the standalone Chromium, too.)

> an OS with just Firefox would really make everything simpler

It's relatively easy to build a Linux distro that boots straight into Firefox! You can try Cubic, which allows you to create a custom ISO for Debian or Ubuntu with a pretty straightforward GUI wizard. I once used it to create an ISO for an arcade machine.

[1]: https://github.com/PJ-Singh-001/Cubic

Gotcha, Cubic might be what you're looking for then. Found it looking for a similar Fedora alternative a while back.

You'll most likely want something like CubicCubic as it just let's you customise any Debian based distro to your needs to become a live iso with a nice GUI or command line access.

I can speak to this. Containers, and by extension k8s, break a well known security boundary that has existed for a very long time - whether you are using a real (hardware) server or a virtual machine on the cloud if you pop that instance/server generally speaking you only have access to that server. Yeh, you might find a db config with connection details if you landed on say a web app host but in general you still have to work to start popping the next N servers.

That's not the case when you are running in k8s and the last container breakout was just announced ~1 month ago: https://github.com/opencontainers/runc/security/advisories/G... .

At the end of the day it is simply not a security boundary. It can solve other problems but not security ones.

It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C)

As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun) this year(https://cloud.redhat.com/blog/whats-new-in-red-hat-openshift...), which is written in C as an alternative to runc, which is written in Go(https://github.com/opencontainers/runc)...

Rabbit hole indeed. That wasn't related to my job at the time, lol. The job change came with a company-provided computer and that put an end to the tinkering.

BTW, I found my hacks to make runc run on Chromebook: https://github.com/opencontainers/runc/compare/main...gabrys...

being the main author of crun, I can clarify that statement: I am not a fan of Go _for this particular use case_.

Using C instead of Go avoided a bunch of the workarounds that exists in runc to workaround the Go runtime, e.g. https://github.com/opencontainers/runc/blob/main/libcontaine...

runc

Not OP, but if I had to guess, a lot of this can be picked up by just observing common security issues in the Linux space, since similar mistakes and oversights have caused quite a few real-world CVEs in the past, e.g. this random example of a TOCTTOU vulnerability in runc.