| /kernel/linux/linux-5.10/drivers/memory/tegra/ |
| D | tegra186.c | 25 unsigned int security; member
47 u32 override, security; in tegra186_mc_program_sid() local
50 security = readl(mc->regs + client->regs.security); in tegra186_mc_program_sid()
52 dev_dbg(mc->dev, "client %s: override: %x security: %x\n", in tegra186_mc_program_sid()
53 client->name, override, security); in tegra186_mc_program_sid()
60 security = readl(mc->regs + client->regs.security); in tegra186_mc_program_sid()
62 dev_dbg(mc->dev, "client %s: override: %x security: %x\n", in tegra186_mc_program_sid()
63 client->name, override, security); in tegra186_mc_program_sid()
74 .security = 0x004,
81 .security = 0x074,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/security/ |
| D | lsm.rst | 2 Linux Security Modules: General Security Hooks for Linux
16 In March 2001, the National Security Agency (NSA) gave a presentation
17 about Security-Enhanced Linux (SELinux) at the 2.5 Linux Kernel Summit.
20 implemented as its own particular kernel patch. Several other security
25 patch to support its security needs.
28 remarks that described a security framework he would be willing to
30 general framework that would provide a set of security hooks to control
31 operations on kernel objects and a set of opaque security fields in
32 kernel data structures for maintaining security attributes. This
34 desired model of security. Linus also suggested the possibility of
[all …]
|
| /kernel/linux/linux-5.10/security/ |
| D | Kconfig | 3 # Security configuration
6 menu "Security options"
8 source "security/keys/Kconfig"
22 config SECURITY config
23 bool "Enable different security models"
27 This allows you to choose different security modules to be
30 If this option is not selected, the default Linux security
36 depends on SECURITY
44 various security modules (AppArmor, IMA, SafeSetID, TOMOYO, TPM).
49 bool "Socket and Networking Security Hooks"
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | lsm_hooks.h | 2 * Linux Security Module interfaces
28 #include <linux/security.h>
33 * union security_list_options - Linux Security Module hook function list
35 * Security hooks for program execution operations.
38 * If the setup in prepare_exec_creds did not setup @bprm->cred->security
40 * @bprm->cred->security to be what commit_creds needs to install for the
42 * (e.g. for transitions between security domains).
55 * between security domains).
64 * begin. It allows a check against the @bprm->cred->security value
71 * Prepare to install the new security attributes of a process being
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/nvdimm/ |
| D | security.rst | 2 NVDIMM Security
9 specification [1], security DSMs are introduced. The spec added the following
10 security DSMs: "get security state", "set passphrase", "disable passphrase",
12 data structure has been added to struct dimm in order to support the security
17 The "security" sysfs attribute is provided in the nvdimm sysfs directory. For
19 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/nmem0/security
21 The "show" attribute of that attribute will display the security state for
23 frozen, and overwrite. If security is not supported, the sysfs attribute
27 in order to support some of the security functionalities:
29 disable <keyid> - disable enabled security and remove key.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/netlabel/ |
| D | lsm_interface.rst | 2 NetLabel Linux Security Module Interface
12 NetLabel is a mechanism which can set and retrieve security attributes from
15 The NetLabel security module API is defined in 'include/net/netlabel.h' but a
18 NetLabel Security Attributes
22 it uses the concept of security attributes to refer to the packet's security
23 labels. The NetLabel security attributes are defined by the
25 NetLabel subsystem converts the security attributes to and from the correct
28 security attributes into whatever security identifiers are in use for their
44 label and the internal LSM security identifier can be time consuming. The
47 LSM has received a packet, used NetLabel to decode its security attributes,
[all …]
|
| D | introduction.rst | 12 NetLabel is a mechanism which can be used by kernel security modules to attach
13 security attributes to outgoing network packets generated from user space
14 applications and read security attributes from incoming network packets. It
16 layer, and the kernel security module API.
22 network packet's security attributes. If any translation between the network
23 security attributes and those on the host are required then the protocol
26 the NetLabel kernel security module API described below.
41 Security Module API
44 The purpose of the NetLabel security module API is to provide a protocol
46 to protocol independence, the security module API is designed to be completely
[all …]
|
| D | draft-ietf-cipso-ipsecurity-01.txt | 6 COMMERCIAL IP SECURITY OPTION (CIPSO 2.2)
13 IP Security Option (CIPSO). This draft reflects the version as approved by
35 Currently the Internet Protocol includes two security options. One of
36 these options is the DoD Basic Security Option (BSO) (Type 130) which allows
37 IP datagrams to be labeled with security classifications. This option
38 provides sixteen security classifications and a variable number of handling
39 restrictions. To handle additional security information, such as security
40 categories or compartments, another security option (Type 133) exists and
41 is referred to as the DoD Extended Security Option (ESO). The values for
46 mandatory access controls and multi-level security. These systems are
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 9 Hardware issues which result in security problems are a different category
10 of security bugs than pure software bugs which only affect the Linux
25 The Linux kernel hardware security team is separate from the regular Linux
26 kernel security team.
28 The team only handles the coordination of embargoed hardware security
29 issues. Reports of pure software security bugs in the Linux kernel are not
31 Linux kernel security team (:ref:`Documentation/admin-guide/
34 The team can be contacted by email at <hardware-security@kernel.org>. This
35 is a private list of security officers who will help you to coordinate an
43 - PGP: https://www.kernel.org/static/files/hardware-security.asc
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | security-bugs.rst | 3 Security bugs
6 Linux kernel developers take security very seriously. As such, we'd
7 like to know when a security bug is found so that it can be fixed and
8 disclosed as quickly as possible. Please report security bugs to the
9 Linux kernel security team.
14 The Linux kernel security team can be contacted by email at
15 <security@kernel.org>. This is a private list of security officers
19 security team will bring in extra help from area maintainers to
20 understand and fix the security vulnerability.
39 The security list is not a disclosure channel. For that, see Coordination
[all …]
|
| /kernel/linux/linux-5.10/security/integrity/evm/ |
| D | Kconfig | 11 EVM protects a file's security extended attributes against
37 In addition to the original security xattrs (eg. security.selinux,
38 security.SMACK64, security.capability, and security.ima) included
40 Smack xattrs: security.SMACK64EXEC, security.SMACK64TRANSMUTE and
41 security.SMACK64MMAP.
56 /sys/kernel/security/integrity/evm/evm_xattrs.
|
| /kernel/liteos_a/security/ |
| D | Kconfig | 1 config SECURITY config
2 bool "Enable Security Module"
5 This option will enable security module. This is a basic feature,
11 depends on SECURITY
19 depends on SECURITY
25 bool "Enable security boot"
27 depends on SECURITY
29 This option will enable security boot.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/LSM/ |
| D | index.rst | 2 Linux Security Module Usage
5 The Linux Security Module (LSM) framework provides a mechanism for
6 various security checks to be hooked by new kernel extensions. The name
10 ``"security=..."`` kernel command line argument, in the case where multiple
14 (MAC) extensions which provide a comprehensive security policy. Examples
25 A list of the active security modules can be found by reading
26 ``/sys/kernel/security/lsm``. This is a comma separated list, and
32 Process attributes associated with "major" security modules should
34 A security module may maintain a module specific subdirectory there,
36 security module and contains all its special files. The files directly
|
| D | apparmor.rst | 8 AppArmor is MAC style security extension for the Linux kernel. It implements
19 If AppArmor should be selected as the default security module then set::
26 If AppArmor is not the default security module it can be enabled by passing
27 ``security=apparmor`` on the kernel's command line.
29 If AppArmor is the default security module it can be disabled by passing
30 ``apparmor=0, security=XXXX`` (where ``XXXX`` is valid security module), on the
|
| /kernel/linux/linux-5.10/security/selinux/ |
| D | xfrm.c | 3 * NSA Security-Enhanced Linux (SELinux) security module
29 * 3. Testing addition of sk_policy's with security context via setsockopt
33 #include <linux/security.h>
63 * Returns true if the xfrm contains a security blob for SELinux.
67 return selinux_authorizable_ctx(x->security); in selinux_authorizable_xfrm()
71 * Allocates a xfrm_sec_state and populates it using the supplied security
183 if (!xp->security) in selinux_xfrm_state_pol_flow_match()
184 if (x->security) in selinux_xfrm_state_pol_flow_match()
191 if (!x->security) in selinux_xfrm_state_pol_flow_match()
199 state_sid = x->security->ctx_sid; in selinux_xfrm_state_pol_flow_match()
[all …]
|
| /kernel/linux/linux-5.10/fs/cachefiles/ |
| D | security.c | 2 /* CacheFiles security management
13 * determine the security context within which we access the cache from within
33 pr_err("Security denies permission to nominate security context: error %d\n", in cachefiles_get_security_ID()
56 pr_err("Security denies permission to make dirs: error %d", in cachefiles_check_cache_dir()
63 pr_err("Security denies permission to create files: error %d", in cachefiles_check_cache_dir()
70 * check the security details of the on-disk cache
71 * - must be called with security override in force
72 * - must return with a security override in force - even in the case of an
92 /* use the cache root dir's security context as the basis with in cachefiles_determine_cache_security()
|
| /kernel/linux/linux-5.10/drivers/crypto/allwinner/ |
| D | Kconfig | 9 tristate "Support for Allwinner Security System cryptographic accelerator"
20 Security System. Select this if you want to use it.
21 The Security System handle AES/DES/3DES ciphers in CBC mode
28 bool "Support for Allwinner Security System PRNG"
33 the Pseudo-Random Number Generator found in the Security System.
89 tristate "Support for Allwinner Security System cryptographic offloader"
99 Select y here to have support for the Security System available on
101 The Security System handle AES/3DES ciphers in ECB/CBC mode.
116 bool "Support for Allwinner Security System PRNG"
121 the Pseudo-Random Number Generator found in the Security System.
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | rxrpc.h | 33 #define RXRPC_SECURITY_KEY 1 /* [clnt] set client security key */
34 #define RXRPC_SECURITY_KEYRING 2 /* [srvr] set ring of server security keys */
36 #define RXRPC_MIN_SECURITY_LEVEL 4 /* minimum security level */
63 * RxRPC security levels
70 * RxRPC security indices
72 #define RXRPC_SECURITY_NONE 0 /* no security protocol */
102 * Rx kerberos security abort codes
103 * - unfortunately we have no generalised security abort codes to say things
104 * like "unsupported security", so we have to use these instead and hope the
107 #define RXKADINCONSISTENCY 19270400 /* security module structure inconsistent */
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/caching/ |
| D | cachefiles.rst | 23 (*) Security model and SELinux.
25 (*) A note on security.
291 Security Model and SELinux
294 CacheFiles is implemented to deal properly with the LSM security features of
299 security context that is not appropriate for accessing the cache - either
304 The way CacheFiles works is to temporarily change the security context (fsuid,
305 fsgid and actor security label) that the process acts as - without changing the
306 security context of the process when it the target of an operation performed by
312 (1) Finds the security label attached to the root cache directory and uses
313 that as the security label with which it will create files. By default,
[all …]
|
| /kernel/linux/linux-5.10/fs/ceph/ |
| D | Kconfig | 41 bool "CephFS Security Labels"
42 depends on CEPH_FS && SECURITY
44 Security labels support alternative access control models
45 implemented by security modules like SELinux. This option
46 enables an extended attribute handler for file security
49 If you are not using a security module that requires using
50 extended attributes for file security labels, say N.
|
| /kernel/linux/linux-5.10/security/tomoyo/ |
| D | securityfs_if.c | 3 * security/tomoyo/securityfs_if.c
8 #include <linux/security.h>
29 * tomoyo_write_self - write() for /sys/kernel/security/tomoyo/self_domain interface.
91 * tomoyo_read_self - read() for /sys/kernel/security/tomoyo/self_domain interface.
118 /* Operations for /sys/kernel/security/tomoyo/self_domain interface. */
125 * tomoyo_open - open() for /sys/kernel/security/tomoyo/ interface.
140 * tomoyo_release - close() for /sys/kernel/security/tomoyo/ interface.
152 * tomoyo_poll - poll() for /sys/kernel/security/tomoyo/ interface.
166 * tomoyo_read - read() for /sys/kernel/security/tomoyo/ interface.
182 * tomoyo_write - write() for /sys/kernel/security/tomoyo/ interface.
[all …]
|
| /kernel/linux/linux-5.10/fs/ext2/ |
| D | Kconfig | 32 bool "Ext2 Security Labels"
35 Security labels support alternative access control models
36 implemented by security modules like SELinux. This option
37 enables an extended attribute handler for file security
40 If you are not using a security module that requires using
41 extended attributes for file security labels, say N.
|
| /kernel/linux/linux-5.10/net/netfilter/ |
| D | xt_CONNSECMARK.c | 3 * This module is used to copy security markings from packets
4 * to connections, and restore security markings from connections
24 MODULE_DESCRIPTION("Xtables: target for copying between connection and security mark");
29 * If the packet has a security mark and the connection does not, copy
30 * the security mark from the packet to the connection.
47 * If packet has no security mark, and the connection does, restore the
48 * security mark from the connection to the packet.
89 strcmp(par->table, "security") != 0) { in connsecmark_tg_check()
90 pr_info_ratelimited("only valid in \'mangle\' or \'security\' table, not \'%s\'\n", in connsecmark_tg_check()
|
| /kernel/linux/linux-5.10/fs/9p/ |
| D | Kconfig | 35 bool "9P Security Labels"
38 Security labels support alternative access control models
39 implemented by security modules like SELinux. This option
40 enables an extended attribute handler for file security
43 If you are not using a security module that requires using
44 extended attributes for file security labels, say N.
|
| /kernel/linux/linux-5.10/drivers/char/tpm/ |
| D | Kconfig | 13 If you have a TPM security chip in your system, which
52 If you have a TPM security chip that is compliant with the
63 If you have a TPM security chip which is connected to a regular,
82 If you have a TPM security chip that is compliant with the
93 If you have an Atmel I2C TPM security chip say Yes and it will be
102 If you have a TPM security chip that is compliant with the
113 If you have a TPM security chip with an I2C interface from
123 If you have a TPM security chip from National Semiconductor
132 If you have a TPM security chip from Atmel say Yes and it
140 If you have a TPM security chip from Infineon Technologies
[all …]
|