KernelSU is pretty interesting in certain circumstances compared to say, Magisk, which is a systemless root. KernelSU cannot be prevented by SELinux—the kernel can even disable SELinux if it wants to.
It's quite useful for gaining root on "weird" and or/old android devices such as lesser-known smartwatches, often that have no support for Magisk at all.
In terms of bypassing SafetyNet, both KernelSU and Magisk have their own strengths and limitations. For those utilizing an Android smartphone in a conventional manner, Magisk may be the preferred choice due to its extensive module support and strong community support.
Most probably not. Kernel devs are tame even with closed-source device and software vendors pirating the Linux kernel. I doubt any kernel copyright holder will bat an eye over GPLv3 vs. GPLv2. Not to mention the very relevant question of "is it really a derivative work?", which very much depends on the depth and complexity of integration, provided interfaces, GPLONLY symbols and other minutiae.
> I doubt any kernel copyright holder will bat an eye over GPLv3 vs. GPLv2.
Probably not, but why risk it? The only meaningful difference between the two is the anti-TiVoization clause, and considering how thoroughly Android is already TiVoized, that seems pretty pointless anyway.
> Not to mention the very relevant question of "is it really a derivative work?", which very much depends on the depth and complexity of integration, provided interfaces, GPLONLY symbols and other minutiae.
It's a kernel module, the build process for which entailing pulling the KernelSU code into a cloned Linux repo. It's pretty unambiguously a derivative work.
It does not grant root by default, quote: "Whitelist access control
Only App that is granted root permission can access `su`, other apps cannot perceive su."
But that's the whole point? That you can user your own device as a general-purpose computing device, not only as a media-consumption device limited by arbitrary restrictions the vendor of the device can pose on you?
What attack do you see this allowing that wouldn't work without it? Considering that the user has to intentionally add it, and the user has to explicitly give apps root access, the only problem I can see is if a user gives root to an untrustworthy app, but that seems like a good trade.
Incidentally, do you also think that users shouldn't have admin power on, say, laptops, or are phones special?
LineageOS hasn't supported root for several major releases. The last official su addon is for version 16.0, https://download.lineageos.org/extras , we are now at 19.1 or 20.0. Magisk used to work, but is getting more and more of a hassle to install and update.
I fear root is becoming rarer and harder, even on alternative Android distributions.
The latest officially avaiable su package is for 16.0. My phone's on 18.1 and the latest version is 20.
If you want SU on a supported LineageOS, you have to use Magisk or potentially this project.
It's quite useful for gaining root on "weird" and or/old android devices such as lesser-known smartwatches, often that have no support for Magisk at all.
In terms of bypassing SafetyNet, both KernelSU and Magisk have their own strengths and limitations. For those utilizing an Android smartphone in a conventional manner, Magisk may be the preferred choice due to its extensive module support and strong community support.