Skip to content
Snippets Groups Projects
Commit 1f6018ea authored by Tom Cherry's avatar Tom Cherry
Browse files

Allow vendor_init to write to misc_block_device

Vendors may use this to write custom messages to their bootloader, and
as the bootloader is under vendor control, this makes sense to allow.

Bug: 77881566
Test: build
Merged-In: I78f80400e5f386cad1327a9209ee1afc8e334e56
Change-Id: I78f80400e5f386cad1327a9209ee1afc8e334e56
(cherry picked from commit db465285)
parent dc3e1dad
No related branches found
No related tags found
No related merge requests found
...@@ -597,6 +597,7 @@ neverallow { ...@@ -597,6 +597,7 @@ neverallow {
-init -init
-uncrypt -uncrypt
-update_engine -update_engine
-vendor_init
-vold -vold
-recovery -recovery
-ueventd -ueventd
......
...@@ -146,6 +146,9 @@ allow vendor_init serialno_prop:file { getattr open read }; ...@@ -146,6 +146,9 @@ allow vendor_init serialno_prop:file { getattr open read };
# Vendor init can perform operations on trusted and security Extended Attributes # Vendor init can perform operations on trusted and security Extended Attributes
allow vendor_init self:global_capability_class_set sys_admin; allow vendor_init self:global_capability_class_set sys_admin;
# Raw writes to misc block device
allow vendor_init misc_block_device:blk_file w_file_perms;
not_compatible_property(` not_compatible_property(`
set_prop(vendor_init, { set_prop(vendor_init, {
property_type property_type
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment