3 ms·
In your opinion, do you think that the microkernel approach is more secure? (Should processes run as separate users with separate SELinux contexts like Android
by westurner 4y ago
In your opinion, do you think that the microkernel approach is more secure? (Should processes run as separate users with separate SELinux contexts like Android 4.4+)
Why do you think that the Android binder module rust implementation is listed as an example of a Rust for Linux kernel module on the site?
"Android AOSP Can Boot Off Mainline Linux 5.9 With Just One Patch" (2020)
https://www.phoronix.com/news/Android-AOSP-Close-Linux-5.9 https://www.phoronix.com/news/Android-AOSP-Close-Linux-5.9 :
> The Android open-source project "AOSP" with its latest code is very close to being able to boot off the mainline Linux kernel when assuming the device drivers are all upstream.
Other distros support kmods and akmods:
https://www.reddit.com/r/PINE64official/comments/ijfbgl/comment/g3dqks6/ https://www.reddit.com/r/PINE64official/comments/ijfbgl/comm... :
> How kmod / akmod // DKMS work is something that the community is maybe not real familiar with.
- pjmlp 4y agoOf course microkernel approach is more secure, if a driver gets p0wned, corrupts data structures, or plain keeps crashing, it doesn't take the whole kernel with it. Naturally the issue might be as bad that the whole stack can't recover from, but still much better than corrupting the kernel. One of the SecDevOps guidelines when hardening servers is that every process should have its own user, yes. Kmods and akmods run in kernel memory space and aren't ABI stable.