The error message suggests how oww to fix it. In your device-specific
selinux policy, you need to add the suggested attributes. e.g.
Change:
type sysfs_sec, file_type;
To:
type sysfs_sec, file_type, sysfs_type;
Similarly add core_data_file_type for gps_data_file and tee_data_file.
On
See https://source.android.com/security/selinux/device-policy
On Tue, Jul 16, 2019 at 11:22 AM Shilesh Babu
wrote:
> Hi guys,
> I am not able to add service properly in init.rc, could you please share
> any information like how to add and crate selinux policy.
> I am doing.
> service
Hi guys,
I am not able to add service properly in init.rc, could you please share
any information like how to add and crate selinux policy.
I am doing.
service testapp /system/bin/testapp //adding in init.rc
Created policy in /device/../sepolicy/testapp.te
Working on Android 8, please let me
Android 9 did not support the hwaddress sanitizer, I believe that support
is in AOSP master, and should be in the Q release.
- Dan
On Tue, Jul 16, 2019 at 9:08 AM H Sai Manikanta Eadapalapati <
saimanika...@eximiusdesign.com> wrote:
> I'm trying to boot the pixel3 xl with aosp hwasan build, for
Hi,
To follow up here as well, a problem with that check is that it's
susceptible to "garbage" output from make targets into $TARGET_OUT. E.g. if
you do "m libcapstone" you'll get the lib in system/lib(64) where it
shouldn't be, and if you after that try "m systemimage" (or "m droid" or
just
Im trying to build AOSPextended but the build fails with this error:
FAILED: /home/simon/AOSP_Extended/out/target/product/a5y17lte/obj/ETC/
sepolicy_tests_intermediates/sepolicy_tests
/bin/bash -c "(/home/simon/AOSP_Extended/out/host/linux-x86/bin/sepolicy_tests
-l
I'm trying to boot the pixel3 xl with aosp hwasan build, for that I took
the latest build
https://source.android.com/setup/start/build-numbers.html#source-code-tags-and-builds
PQ3A.190705.003 android-9.0.0_r44 Pie Pixel 3 XL, Pixel 3 2019-07-05
I'm getting an error as "unknown global sanitizer
Thanks for your reply.
Our purpose is to generate "License checking code" for specific product
build.
So we have a shell script to generate the code based on the PRODUCT_XXX
properties.
Are you implying that Android.bp should only be used in generic (product
independent) modules?
And this kind
