diff options
| author | Nick Kralevich <nnk@google.com> | 2019-05-14 09:23:26 -0700 |
|---|---|---|
| committer | Nick Kralevich <nnk@google.com> | 2019-05-14 09:23:26 -0700 |
| commit | 2d3cc3b458831550a4a1caccd03c98a4a0def064 (patch) | |
| tree | 2ecfaa19bf4dc146728098ded1660548910f9344 /libselinux/man/man8 | |
| parent | 4a792614521f82ffa73448483071925a2b77315b (diff) | |
| download | android_external_selinux-2d3cc3b458831550a4a1caccd03c98a4a0def064.tar.gz android_external_selinux-2d3cc3b458831550a4a1caccd03c98a4a0def064.tar.bz2 android_external_selinux-2d3cc3b458831550a4a1caccd03c98a4a0def064.zip | |
Delay /data/vendor_ce restorecon
When Android boots after file_contexts has changed, the boot process
walks the entire /data partition, updating any changed SELinux labels as
appropriate. However, credential encrypted ("ce") directories are
deliberately excluded from this early boot directory walk. Files within
ce directories have their filenames encrypted, and as a result, cannot
match the file_contexts entries. Only after the user has unlocked their
device are the unencrypted filenames available and a restorecon
appropriate.
Exclude /data/vendor_ce from the early boot restorecon, like we do for
/data/system_ce and /data/misc_ce. This prevents init from
inappropriately relabeling these files with encrypted filenames.
Bug: 132349934
Test: See bug 132349934 comment #12 for test procedure
Change-Id: I59171f11dc25d446fae3760c4aa538264944391d
Diffstat (limited to 'libselinux/man/man8')
0 files changed, 0 insertions, 0 deletions