kernel-assisted-superuser, branch masterKernel assisted means of gaining a root shell for Androidhttps://git.zx2c4.com/kernel-assisted-superuser/atom/?h=master2018-12-04T02:03:12ZUse real su if it exists2018-12-04T02:03:12ZJason A. DonenfeldJason@zx2c4.com2018-12-04T02:03:12Zurn:sha1:5586a6cb16780985e82d449a581beb203d521eaa
In case we already have su from elsewhere, use it instead.
Wrap at 80 chars2018-11-25T17:36:37ZJason A. DonenfeldJason@zx2c4.com2018-11-25T17:36:37Zurn:sha1:9102112c620df22e0e0c1fa6b6d4851d8ffb0b18Depend on SECURITY_SELINUX_DEVELOP2018-11-25T17:31:14ZJason A. DonenfeldJason@zx2c4.com2018-11-25T17:31:14Zurn:sha1:697ea49b5bdffa93e5654191bac3d80647d73368
We eventually want to load an selinux policy and attach it to the cred,
so as to not disable it globally, but for now this will do.
Suggested-by: Sultan Alsawaf <sultan@kerneltoast.com>
Use sys_write instead of kernel_write2018-11-23T17:27:19ZJason A. DonenfeldJason@zx2c4.com2018-11-23T02:41:11Zurn:sha1:3564c6dcc370d3d1e43913db45b2ea16e8c26662
This is mostly worse in all ways, except that we don't have to worry
about the API of kernel_write changing between kernels, which has
happened before.
Write below stack pointer instead of mmapping2018-11-23T17:27:19ZJason A. DonenfeldJason@zx2c4.com2018-11-23T02:21:34Zurn:sha1:48bc55f87e4926dc3d08366fb16d024ad61bb942Hijack `su` instead.2018-11-23T17:27:19ZJason A. DonenfeldJason@zx2c4.com2018-11-23T01:06:09Zurn:sha1:5f1cd1caed2033ae1aabdda440e39e2b0b733a52Initial commit2018-11-22T21:39:25ZJason A. DonenfeldJason@zx2c4.com2018-11-22T18:14:34Zurn:sha1:eb3ce67ef709a2550e0da613021bf9dacb79d095