Hi,
I was looking at system/core/init/init.c. It seems that SEAndroid policy is
being loaded from here and hence enforced. Is not it that attacker can
replace init.c with the one not enforcing selinux policy? If it is true,
how seandroid is secure. if not true, what am I missing? Or is it that
init.c goes inside boot.img which is signed and hence image is verified
during boot load and there is no way attacker can replace init.c ?

Thanks,
Dinesh
_______________________________________________
Seandroid-list mailing list
[email protected]
To unsubscribe, send email to [email protected].
To get help, send an email containing "help" to 
[email protected].

Reply via email to