Hi, Recent changes to AOSP master, our seandroid branch, and our seandroid-4.4.2 branch have placed the processes running on the recovery image into their own security contexts. Previously they were just left running in the kernel domain as there was no setcon command or seclabel definitions in the recovery init.rc file. If using our seandroid-4.4.2 branch, you will need to update your local_manifest.xml file in order to pick up the modifications for the bootable/recovery project.
The changes are required in order to enable continued operation of the recovery console after recent changes made to remove specific permissions from unconfineddomain. If you happened to sync earlier, tried booting into recovery, and found yourself with a non-functional recovery (i.e. no UI), it was due to the removal of these permissions without having separate policy for the recovery console. In that situation, it is necessary to reflash with a working recovery and clear the cache partition in order to proceed. If you have problems with the recovery policy, let us know. Thanks. _______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
