Searched refs:may (Results 1 – 12 of 12) sorted by relevance
/security/smack/ |
D | smack_access.c | 89 int may = srp->smk_access; in smk_access_entry() local 93 if ((may & MAY_WRITE) == MAY_WRITE) in smk_access_entry() 94 may |= MAY_LOCK; in smk_access_entry() 95 return may; in smk_access_entry() 118 int may = MAY_NOT; in smk_access() local 168 may = smk_access_entry(subject->smk_known, object->smk_known, in smk_access() 172 if (may <= 0 || (request & may) != request) { in smk_access() 182 if (may & MAY_BRINGUP) in smk_access() 222 int may; in smk_tskacc() local 234 may = smk_access_entry(sbj_known->smk_known, in smk_tskacc() [all …]
|
D | smack_lsm.c | 1007 int may; in smack_inode_init_security() local 1019 may = smk_access_entry(skp->smk_known, dsp->smk_known, in smack_inode_init_security() 1031 (may > 0 && ((may & MAY_TRANSMUTE) != 0) && in smack_inode_init_security() 1719 int may; in smack_mmap_file() local 1760 may = smk_access_entry(srp->smk_subject->smk_known, in smack_mmap_file() 1763 if (may == -ENOENT) in smack_mmap_file() 1764 may = srp->smk_access; in smack_mmap_file() 1766 may &= srp->smk_access; in smack_mmap_file() 1771 if (may == 0) in smack_mmap_file() 1799 if ((may | mmay) != mmay) { in smack_mmap_file() [all …]
|
D | Kconfig | 28 may be inappropriate. The developer can reduce the
|
/security/selinux/ |
D | Kconfig | 70 /sys/fs/selinux/avc/cache_stats, which may be monitored via 87 The checkreqprot flag may be changed from the default via the 88 'checkreqprot=' boot parameter. It may also be changed at runtime 104 collisions may be viewed at /sys/fs/selinux/ss/sidtab_hash_stats. If
|
/security/tomoyo/ |
D | Kconfig | 14 Required userspace tools and further information may be 40 If you don't need audit logs, you may set this value to 0. 76 option. For example, if you pass init=/bin/systemd option, you may
|
/security/integrity/ |
D | Kconfig | 66 bool "Provide a keyring to which Machine Owner Keys may be added" 73 If set, provide a keyring to which Machine Owner Keys (MOK) may
|
/security/lockdown/ |
D | Kconfig | 30 No lockdown functionality is enabled by default. Lockdown may be
|
/security/keys/ |
D | Kconfig | 51 A particular keyring may be accessed by either the user whose keyring 66 (for example Kerberos ticket caches). The data may be stored out to
|
/security/integrity/ima/ |
D | Kconfig | 176 Depending on the rules configured, this policy may require kernel 253 Keys may be added to the IMA or IMA blacklist keyrings, if the 258 IMA keys to be added may be added to the system secondary keyring,
|
/security/ |
D | Kconfig.hardening | 82 Zero-initialize any structures on the stack that may 101 Zero-initialize any stack variables that may be passed 177 sees a 1% slowdown, other systems and workloads may vary and you 323 structures as much as possible, which may have both a
|
D | Kconfig | 107 it was configured with, especially since they may be responsible for
|
/security/apparmor/ |
D | Kconfig | 13 distribution) and further information may be found at
|