Searched full:security (Results 1 – 25 of 304) sorted by relevance
12345678910>>...13
| /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 …]
|
| D | lsm-development.rst | 2 Linux Security Module Development
14 see ``security/security.c`` and associated structures:
16 .. kernel-doc:: security/security.c
|
| /Documentation/userspace-api/ |
| D | lsm.rst | 6 Linux Security Modules
12 Linux security modules (LSM) provide a mechanism to implement
13 additional access controls to the Linux security policies.
15 The various security modules may support any of these attributes:
17 ``LSM_ATTR_CURRENT`` is the current, active security context of the
20 This is supported by the SELinux, Smack and AppArmor security modules.
24 ``LSM_ATTR_EXEC`` is the security context of the process at the time the
27 This is supported by the SELinux and AppArmor security modules.
30 ``LSM_ATTR_FSCREATE`` is the security context of the process used when
33 This is supported by the SELinux security module.
[all …]
|
| /Documentation/process/ |
| 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 …]
|
| 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 developing fixes for 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 coordinate a fix
43 - PGP: https://www.kernel.org/static/files/hardware-security.asc
[all …]
|
| D | cve.rst | 7 security vulnerabilities. Over time, their usefulness has declined with
12 security identifiers, and ongoing abuses by individuals and companies
17 potential Linux kernel security issues. This assignment is independent
18 of the :doc:`normal Linux kernel security bug reporting
19 process<../process/security-bugs>`.
31 potentially security issues are identified by the developers responsible
37 any bug might be exploitable to compromise the security of the kernel,
47 security issues should be sent to this alias, it is ONLY for assignment
49 feel you have found an unfixed security issue, please follow the
50 :doc:`normal Linux kernel security bug reporting
[all …]
|
| /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 …]
|
| /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 | cipso_ipv4.rst | 13 IP Security Option (CIPSO) draft from July 16, 1992. A copy of this
27 label by using the NetLabel security module API; if the NetLabel "domain" is
37 NetLabel security module API to extract the security attributes of the packet.
44 The CIPSO/IPv4 protocol engine contains a mechanism to translate CIPSO security
49 different security attribute mapping table.
54 The NetLabel system provides a framework for caching security attribute
|
| 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 …]
|
| /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
|
| /Documentation/ABI/testing/ |
| D | procfs-attr-current | 2 Contact: linux-security-module@vger.kernel.org,
5 Description: The current security information used by a Linux
6 security module (LSM) that is active on the system.
8 this interface and hence obtain the security state
13 this interface and hence change the security state of
|
| D | procfs-attr-exec | 2 Contact: linux-security-module@vger.kernel.org,
5 Description: The security information to be used on the process
6 by a Linux security module (LSM) active on the system
9 this interface and hence obtain the security state
14 this interface and hence change the security state of
|
| D | sysfs-driver-intel-m10-bmc-sec-update | 1 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/sr_root_entry_hash
11 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/pr_root_entry_hash
21 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/bmc_root_entry_hash
31 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/sr_canceled_csks
39 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/pr_canceled_csks
47 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/bmc_canceled_csks
55 What: /sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/flash_count
|
| D | evm | 1 What: /sys/kernel/security/evm
2 What: /sys/kernel/security/*/evm
6 EVM protects a file's security extended attributes(xattrs)
9 value as the extended attribute 'security.evm'.
11 EVM supports two classes of security.evm. The first is
85 or validate the 'security.evm' xattr, but returns
92 Documentation/security/keys/trusted-encrypted.rst. Both
97 What: /sys/kernel/security/*/evm/evm_xattrs
|
| D | procfs-attr-prev | 2 Contact: linux-security-module@vger.kernel.org,
5 Description: The security information used on the process by
6 a Linux security module (LSM) active on the system
|
| D | securityfs-secrets-coco | 1 What: security/secrets/coco
29 # ls -l /sys/kernel/security/secrets/coco
37 # cat /sys/kernel/security/secrets/coco/e6f5a162-d67f-4750-a67c-5d065f2a9910
42 # rm /sys/kernel/security/secrets/coco/e6f5a162-d67f-4750-a67c-5d065f2a9910
43 # ls -l /sys/kernel/security/secrets/coco
|
| /Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 35 * If a security fix needs lockstep firmware and kernel fixes in order to
38 should be updated with the security fix. The kernel patches should
39 detect if the firmware is new enough to declare if the security issue
40 is fixed. All communications around security fixes should point at
41 both the firmware and kernel fixes. If a security fix requires
|
| /Documentation/filesystems/caching/ |
| D | cachefiles.rst | 23 (*) Security model and SELinux.
25 (*) A note on security.
292 Security Model and SELinux
295 CacheFiles is implemented to deal properly with the LSM security features of
300 security context that is not appropriate for accessing the cache - either
305 The way CacheFiles works is to temporarily change the security context (fsuid,
306 fsgid and actor security label) that the process acts as - without changing the
307 security context of the process when it the target of an operation performed by
313 (1) Finds the security label attached to the root cache directory and uses
314 that as the security label with which it will create files. By default,
[all …]
|
| /Documentation/translations/zh_CN/process/ |
| D | security-bugs.rst | 5 :Original: :doc:`../../../process/security-bugs`
21 可以通过电子邮件<security@kernel.org>联系Linux内核安全团队。这是一个安全人员
60 公共 "oss-security" 邮件列表进行。两者紧密关联且被展示在 linux-distros 维基：
61 <https://oss-security.openwall.org/wiki/mailing-lists/distros>
|
| /Documentation/devicetree/bindings/bus/ |
| D | st,stm32mp25-rifsc.yaml | 7 title: STM32 Resource isolation framework security controller
17 The RIFSC (RIF security controller) is composed of three sets of registers,
21 any security domains (secure, privilege, compartment).
23 unit), assign all non RIF-aware bus master to one security domain by
30 security domains (secure, privilege, compartment).
|
| /Documentation/admin-guide/ |
| D | thunderbolt.rst | 18 software connection manager in Linux also advertises security level
21 the software connection manager only supports ``user`` security level and
24 Security levels and how to use them
40 keep in mind that this bypasses the security levels and makes the system
44 security levels available. Intel Titan Ridge added one more security level
51 treated as another security level (nopcie).
53 The security levels are as follows:
87 The current security level can be read from
88 ``/sys/bus/thunderbolt/devices/domainX/security`` where ``domainX`` is
92 If the security level reads as ``user`` or ``secure`` the connected
[all …]
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | security-bugs.rst | 5 :Original: :doc:`../../../process/security-bugs`
21 可以通過電子郵件<security@kernel.org>聯繫Linux內核安全團隊。這是一個安全人員
64 <http://oss-security.openwall.org/wiki/mailing-lists/distros#how-to-use-the-lists>。
|
12345678910>>...13