seandroid

问题 I want to excute an executable on boot On a target board with Android 5.1 so I add this in init.rc: on boot start myservice service myservice /system/bin/myservice #class main user root group root #oneshot I did the unpack and repack job. When changes are made, however, the screen keeps printing: init warning: Service myservice needs a SELinux domain defined. Please fix. type=1400 ... avc:denied ... scontext ... tcontext ... #some annoying warning messages like this SELinux seems a huge

问题 I want to excute an executable on boot On a target board with Android 5.1 so I add this in init.rc: on boot start myservice service myservice /system/bin/myservice #class main user root group root #oneshot I did the unpack and repack job. When changes are made, however, the screen keeps printing: init warning: Service myservice needs a SELinux domain defined. Please fix. type=1400 ... avc:denied ... scontext ... tcontext ... #some annoying warning messages like this SELinux seems a huge

问题 I want to excute an executable on boot On a target board with Android 5.1 so I add this in init.rc: on boot start myservice service myservice /system/bin/myservice #class main user root group root #oneshot I did the unpack and repack job. When changes are made, however, the screen keeps printing: init warning: Service myservice needs a SELinux domain defined. Please fix. type=1400 ... avc:denied ... scontext ... tcontext ... #some annoying warning messages like this SELinux seems a huge

问题 I want to excute an executable on boot On a target board with Android 5.1 so I add this in init.rc: on boot start myservice service myservice /system/bin/myservice #class main user root group root #oneshot I did the unpack and repack job. When changes are made, however, the screen keeps printing: init warning: Service myservice needs a SELinux domain defined. Please fix. type=1400 ... avc:denied ... scontext ... tcontext ... #some annoying warning messages like this SELinux seems a huge

问题 I have some trouble on getting custom selinux policies running properly on an AOSP based Android 7.1.2 (more precisely based on sony open devices tree). My problem is that the audit logs keep telling me about missing file access rules that I actually added. I also copied rules that audit2allow has created to my policy files, but even those do not properly work. So, let's dig into the details: I created a custom domain called vendor_app . This domain is assigned to an app based on its