platform_system_core

The use case is not wanting people to care, in theory if you license a small code sample under ISC / MIT / normal BSD, etc. licenses then someone has to include the copyright statement in "all copies" (ISC, or slightly different wording with the others). With 0BSD there's no need to remove the copyright notice, but there's no need to proliferate the text. As mentioned in https://landley.net/toybox/license.html the result of correctly complying with this can be crazy things like: https://github.com/android/platform_system_core/blob/fd4c6b0... The advantage of 0BSD is it appears to be the most accepted OSI license without the attribution requirement (given as you mention CC0 isn't accepted by Fedora, Unlicense isn't allowed by Google). Usual not being a lawyer applies, this is just my observations.

The isolation seems mostly defined by this SELinux policy: https://github.com/android/platform_system_core/blob/lollipo... service media /system/bin/mediaserver class main user media group audio camera inet net_bt net_bt_admin net_bw_acct drmrpc mediadrm ioprio rt 4 You'd need another exploit to elevate from SELinux (and I think send MSSes for a self-propagating worm). Though given Android's abysmal patching, most Android kernels are also terribly outdated...