Searched refs:untrusted (Results 1 – 16 of 16) sorted by relevance
2 ### neverallow rules for untrusted app domains19 # Do not allow untrusted apps to register services.24 # Do not allow untrusted apps to use VendorBinder28 # Do not allow untrusted apps to connect to the property service34 # Do not allow untrusted apps to be assigned mlstrustedsubject.41 # and an untrusted app is allowed fork permission to itself.44 # Do not allow untrusted apps to hard link to any files.45 # In particular, if an untrusted app links to other app data48 # bugs, so we want to ensure untrusted apps never have this52 # Do not allow untrusted apps to access network MAC address file[all …]
11 # domain when working with untrusted block devices
1 # blkid for untrusted block devices
4 ### This file defines the rules shared by all untrusted app domains except21 ### Note that rules that should apply to all untrusted apps must be in app.te or also100 # Allow untrusted apps read / execute access to /vendor/app for there can
4 ### This file defines the rules for untrusted apps.
4 ### This file defines the rules for untrusted apps running with
2 # isolated_app processes for rendering untrusted web content.
323 # device traffic. Do not allow untrusted app to directly open tun_device
1 # Any fsck program run on untrusted block devices
147 # hwservices that are accessible from untrusted applications
417 # Never read/follow symlinks created by shell or untrusted apps.
179 # Allow a base set of permissions required for all untrusted apps.
998 # Profiles contain untrusted data and profman parses that. We should only run
186 std::string& fsUuid, std::string& fsLabel, bool untrusted) { in readMetadata() argument204 status_t res = ForkExecvp(cmd, output, untrusted ? sBlkidUntrustedContext : sBlkidContext); in readMetadata()