mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

15K
active users

#sandboxing

3 posts3 participants0 posts today

@linuxuserspace

Pretty late, but comment to the #Snap and #Flatpak episodes:

My Flatpaks take up 30GB of space, after deduplication. A ton of outdated runtimes (badly maintained packages) and random stuff like #mpv or #ffmpeg shipped with apps instead of as a runtime extension are issues.

And no, you dont need to have an entire #distribution for #sandboxing. You can use #bubblejail and other new tools like #crabjail or #fortify.

For Flatpak and Snap, cross compatibility is 1st priority

1/2

Replied in thread

@bohwaz @punkfairie @ajsadauskas @JessTheUnstill @tomiahonen That's exactly the problem, cuz #KaiOS nee #FirefoxOS was a good and solid basis not just for #LowEnd-Devices but could've been excellent for a more #secure mobile OS, as it has good potential for #sandboxing and #KISS-principle'd #Apps that are lean and efficient.

But then again when enthusiasts like @fuchsiii and I were shouting "#ShutUpAndTakeMyMoney!" to #Mozilla, they basically refused to sell any #device, and then we get the "#PSvita-Effect":

I've seen #AppArmor used primarily to *harden* the security of an existing program. Is it also reasonable to use it to *sandbox* known-malicious code? Or are other methods required?

(I assume you also want ulimit or similar on the side, but that's to prevent resource consumption attacks rather than sandbox escapes.)

Replied in thread

@opensuse

Do you plan on doing more #SELinux hardening than #Fedora does?

Because how it is, SELinux on Fedora just makes #run0 a pain to use, while user processes are all unconfined, making it pretty pointless.

Or do you plan on making it user friendly?

There are many issues with #Flatpak that should be addressed. Alternatively, #UID #Sandboxing using #SimpleSandbox and SELinux could be used, which is way simpler and more secure, but relies on native packages

wiki.gentoo.org/wiki/Simple_sa

wiki.gentoo.orgSimple sandbox - Gentoo wiki

#Syd is a rock-solid application #kernel to sandbox applications on Linux>=5.19. Syd is similar to Bubblewrap, Firejail, GVisor, and minijail. As an application kernel it implements a subset of the Linux kernel interface in user space, intercepting system calls to provide strong isolation without the overhead of full virtualization. Syd is secure by default, and intends to provide a simple interface over various intricate #Linux #sandboxing mechanisms such as LandLock, Namespaces, Ptrace, and Seccomp-{BPF,Notify} gitlab.exherbo.org/sydbox/sydb

GitLabSydbox / sydbox · GitLabrock-solid application kernel
Replied in thread

@ktn @ct_Magazin @heiseonline @jolla

Schon cool. Aber ist es auch annähernd so sicher?

#Android hat einen minimalen #Kernel, und Alternativen für alles mögliche wie glibc/bionic.

Auch der #SELinux support ist einzigartig, nichtmal #Fedora oder #RHEL verwenden SELinux wirklich start zum #sandboxing

Das läuft ohne #usernamespace.s mit separaten #UID.s, eine super simple #Unix-Funktion.

#Bluetooth ist isoliert. #USB-port (bei #GooglePixel mit #GrapheneOS) kann ich in der Hardware ausmachen

Replied in thread

@kde@floss.social @kde@lemmy.kde.social

Can you tell us what happens on the "sandbox all the things" goal?

I think this is a pretty crucial step forward, even though #sandbox technologies (most often through user namespaces) are more problematic than I initially thought.

(Basically, user #namespaces open up #privesc dangers to the monolithic #kernel, which is incredible. #Android and #ChromeOS use #LXC, mounts and #SELinux for #sandboxing)