Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Q-COMPAT] Change toybox run context, update selinux xattr #613

Merged
merged 2 commits into from Jul 29, 2019

Conversation

ix5
Copy link
Contributor

@ix5 ix5 commented May 24, 2019

init: Change toybox SELinux run context

Entering the vendor_init context from other entrypoints is disallowed on Android Q, see:
https://android.googlesource.com/platform/system/sepolicy/+/44328c061d67636d4d8047ac69c4e778467eb4e8/public/vendor_init.te#263

init: Wipe updated xattr from /persist/

restorecon now looks for the security.sehash xattr.

See https://android-review.googlesource.com/c/platform/external/selinux/+/916356


See sonyxperiadev/device-sony-sepolicy#526 for updated sepolicy

ix5 added 2 commits May 24, 2019
Entering the vendor_init context from other entrypoints is disallowed on
Android Q, see:
https://android.googlesource.com/platform/system/sepolicy/+/44328c061d67636d4d8047ac69c4e778467eb4e8/public/vendor_init.te#263

Needs new sepolicy for vendor_toolbox
@ix5 ix5 changed the title [DONOTMERGE] [Q-COMPAT] Change toybox run context [DONOTMERGE] [Q-COMPAT] Change toybox run context, update selinux xattr May 24, 2019
@ix5 ix5 changed the title [DONOTMERGE] [Q-COMPAT] Change toybox run context, update selinux xattr [Q-COMPAT] Change toybox run context, update selinux xattr Jul 29, 2019
@ix5
Copy link
Contributor Author

@ix5 ix5 commented Jul 29, 2019

Can be merged into Pie already.

@jerpelea jerpelea merged commit afc15bf into sonyxperiadev:master Jul 29, 2019
@ix5 ix5 deleted the toolbox-context branch Jul 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants