Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
AndroidSystemSEPolicy
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Werner Sembach
AndroidSystemSEPolicy
Commits
56febcef
Commit
56febcef
authored
8 years ago
by
Treehugger Robot
Committed by
Gerrit Code Review
8 years ago
Browse files
Options
Downloads
Plain Diff
Merge "Let init restorecon /dev/random and /dev/urandom."
parents
62a225ff
ad9c6358
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
init.te
+3
-0
3 additions, 0 deletions
init.te
with
3 additions
and
0 deletions
init.te
+
3
−
0
View file @
56febcef
...
@@ -20,6 +20,9 @@ allow init properties_serial:file { write relabelto };
...
@@ -20,6 +20,9 @@ allow init properties_serial:file { write relabelto };
allow init property_type:file { create_file_perms relabelto };
allow init property_type:file { create_file_perms relabelto };
# /dev/socket
# /dev/socket
allow init { device socket_device }:dir relabelto;
allow init { device socket_device }:dir relabelto;
# /dev/random, /dev/urandom
allow init random_device:chr_file relabelto;
allow init urandom_device:chr_file relabelto;
# /dev/device-mapper, /dev/block(/.*)?
# /dev/device-mapper, /dev/block(/.*)?
allow init tmpfs:{ chr_file blk_file } relabelfrom;
allow init tmpfs:{ chr_file blk_file } relabelfrom;
allow init tmpfs:blk_file getattr;
allow init tmpfs:blk_file getattr;
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment