{"action":"opened","issue":{"url":"https://api.github.com/repos/phhusson/Superuser/issues/4","labels_url":"https://api.github.com/repos/phhusson/Superuser/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/phhusson/Superuser/issues/4/comments","events_url":"https://api.github.com/repos/phhusson/Superuser/issues/4/events","html_url":"https://github.com/phhusson/Superuser/issues/4","id":111237015,"number":4,"title":"Considerations for Android 6.0 support","user":{"login":"lbdroid","id":3372230,"avatar_url":"https://avatars.githubusercontent.com/u/3372230?v=3","gravatar_id":"","url":"https://api.github.com/users/lbdroid","html_url":"https://github.com/lbdroid","followers_url":"https://api.github.com/users/lbdroid/followers","following_url":"https://api.github.com/users/lbdroid/following{/other_user}","gists_url":"https://api.github.com/users/lbdroid/gists{/gist_id}","starred_url":"https://api.github.com/users/lbdroid/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lbdroid/subscriptions","organizations_url":"https://api.github.com/users/lbdroid/orgs","repos_url":"https://api.github.com/users/lbdroid/repos","events_url":"https://api.github.com/users/lbdroid/events{/privacy}","received_events_url":"https://api.github.com/users/lbdroid/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-13T18:10:55Z","updated_at":"2015-10-13T18:10:55Z","closed_at":null,"body":"From what I can tell, the difference between 5.x and 6.0 basically involve a tightened up sepolicy. Specifically (and most likely), things like https://android.googlesource.com/platform/external/sepolicy/+/356df32778732aa576e15071bf2736fbbd778b77%5E!/#F0\r\n\r\nThe evil closed source supersu has implemented a sepolicy patcher in their \"supolicy\" command. It takes the factory sepolicy file and generates a \"patched\" sepolicy that works with the rest of their code. HOWEVER, they refuse to even document the changes they are making to the sepolicy, which makes it impossible to trust them.\r\n\r\nIt is likely that a similar policy patch will be required. It should be possible to build it into an update zip that can repack the boot.img similar to things like http://forum.xda-developers.com/nexus-6/development/fix-fed-patcher-forceencrypt-disable-t3203867\r\n\r\nI also suggest that consideration should be made to having the *entire* su system (save for the android apk) made part of the boot.img rather than breaking dmverity on the system partition. Since the boot.img will require modification either way, it is trivial to add the rest in there. Possibly even simplifies the process, since there are other hijacks made available for obtaining the init context from the boot.img."}}