Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
sepolicy
Manage
Activity
Members
Plan
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CodeLinaro
public-release-test
platform
system
sepolicy
Commits
98c3f997
Commit
98c3f997
authored
9 years ago
by
Jeffrey Vander Stoep
Committed by
Gerrit Code Review
9 years ago
Browse files
Options
Downloads
Plain Diff
Merge "Further restrict access to tun_device"
parents
6fa6bdb6
e555f4b9
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
app.te
+3
-0
3 additions, 0 deletions
app.te
bluetooth.te
+1
-6
1 addition, 6 deletions
bluetooth.te
untrusted_app.te
+0
-3
0 additions, 3 deletions
untrusted_app.te
with
4 additions
and
9 deletions
app.te
+
3
−
0
View file @
98c3f997
...
@@ -396,3 +396,6 @@ neverallow appdomain {
...
@@ -396,3 +396,6 @@ neverallow appdomain {
security_file
security_file
tmpfs
tmpfs
}:lnk_file no_w_file_perms;
}:lnk_file no_w_file_perms;
# Do not allow Apps to directly open tun_device
neverallow appdomain tun_device:chr_file open;
This diff is collapsed.
Click to expand it.
bluetooth.te
+
1
−
6
View file @
98c3f997
...
@@ -16,12 +16,7 @@ allow bluetooth bluetooth_socket:sock_file create_file_perms;
...
@@ -16,12 +16,7 @@ allow bluetooth bluetooth_socket:sock_file create_file_perms;
# bluetooth factory file accesses.
# bluetooth factory file accesses.
r_dir_file(bluetooth, bluetooth_efs_file)
r_dir_file(bluetooth, bluetooth_efs_file)
# TODO why does bluetooth require access to tun_device? If not,
allow bluetooth { uhid_device hci_attach_dev }:chr_file rw_file_perms;
# remove access and tighten down neverallow rule so that appdomain is
# not allowed to open (as opposed to just untrusted_app)
# Device accesses. b/24744295
allow bluetooth { tun_device uhid_device hci_attach_dev }:chr_file rw_file_perms;
auditallow bluetooth tun_device:chr_file rw_file_perms;
# sysfs access.
# sysfs access.
allow bluetooth sysfs_bluetooth_writable:file rw_file_perms;
allow bluetooth sysfs_bluetooth_writable:file rw_file_perms;
...
...
This diff is collapsed.
Click to expand it.
untrusted_app.te
+
0
−
3
View file @
98c3f997
...
@@ -145,9 +145,6 @@ neverallow untrusted_app file_type:file link;
...
@@ -145,9 +145,6 @@ neverallow untrusted_app file_type:file link;
# Do not allow untrusted_app to access network MAC address file
# Do not allow untrusted_app to access network MAC address file
neverallow untrusted_app sysfs_mac_address:file no_rw_file_perms;
neverallow untrusted_app sysfs_mac_address:file no_rw_file_perms;
# Do not allow untrusted app to directly open tun_device
neverallow untrusted_app tun_device:chr_file open;
# Do not allow untrusted_app access to /cache
# Do not allow untrusted_app access to /cache
neverallow untrusted_app cache_file:dir ~{ r_dir_perms };
neverallow untrusted_app cache_file:dir ~{ r_dir_perms };
neverallow untrusted_app cache_file:file ~{ read getattr };
neverallow untrusted_app cache_file:file ~{ read 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