3 ms·
Because Linux userspace arguably sucks. While the kernel is excellent, there is no sane sandboxing (and I can’t communicate enough how truly terrible linux desk
by kaba0 5y ago
Because Linux userspace arguably sucks. While the kernel is excellent, there is no sane sandboxing (and I can’t communicate enough how truly terrible linux desktop’s “security” is. A single bash script could break absolute havoc), the IPC mechanism used to communicate between programs is fragmented and in my opinion the insistence that C should be used everywhere really holds back the platform.
Compared to that, android has a well-architected sandboxing with very gradual permissions, SELinux for the remaining features (sure, mainline linux distros also have it from time-to-time but it is not used there to its full extent. Android runs every application as a different user for example, making security boundaries much more explicit), so I would rather ask, why doesn’t mainline linux copy some things from android?
Also, don’t get me wrong, I really like using linux OSs, but they do have plenty of space to improve.
- zozbot234 5y agoMost Linux distros have standardized on AppArmor which provides the same basic featureset as SELinux while being a lot easier to manage (e.g. no file system hacks required, everything is set up via standard configuration mechanisms!).
- nyanpasu64 5y ago> why doesn’t mainline linux copy some things from android? Because Android is actively interfering with: - a shared filesystem where you can manage files from a graphical file manager, terminal, Git, editor/IDE, compiler, Python runtime, photo manager, and hex editor - Being able to debug apps from other apps (Mac disables lldb altogether unless you disable SIP, then you need to type your password every time, and Android ships with no debugging tools at all)
- kaba0 5y ago> a shared filesystem There is absolutely zero reason for any random app to have access to arbitrary files on my computer. Why should a random bash script be able to wipe out all my family pictures? Also, there is nothing inherent in the android model that would make a “shared filesystem” infeasible - it is just the wrong default. With specific access rights sure, it should be allowed.