Searched refs:LSM (Results 1 – 25 of 56) sorted by relevance
123
| /Linux-v6.1/Documentation/netlabel/ |
| D | lsm_interface.rst | 13 network packets. It is intended to be used by LSM developers who want to make
27 configuration. It is up to the LSM developer to translate the NetLabel
29 particular LSM.
31 NetLabel LSM Protocol Operations
34 These are the functions which allow the LSM developer to manipulate the labels
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,
48 and translated the security attributes into a LSM internal identifier the LSM
49 can use the NetLabel caching functions to associate the LSM internal
52 NetLabel translation mechanisms bypassed but the LSM translation mechanisms are
|
| D | cipso_ipv4.rst | 26 that it is set upon the socket's creation. The LSM can set the socket's CIPSO
35 IP layer without any special handling required by the LSM. However, in order
36 to decode and translate the CIPSO label on the packet the LSM must use the
39 LSM hook.
55 mappings from the network labels to the corresponding LSM identifiers. The
|
| /Linux-v6.1/Documentation/admin-guide/LSM/ |
| D | tomoyo.rst | 8 TOMOYO is a name-based MAC extension (LSM module) for the Linux kernel.
15 Though these tutorials use non-LSM version of TOMOYO, they are useful for you
59 multiple LSM modules at the same time. We feel sorry that you have to give up
62 We hope that LSM becomes stackable in future. Meanwhile, you can use non-LSM
64 LSM version of TOMOYO is a subset of non-LSM version of TOMOYO. We are planning
65 to port non-LSM version's functionalities to LSM versions.
|
| D | index.rst | 5 The Linux Security Module (LSM) framework provides a mechanism for
13 The primary users of the LSM interface are Mandatory Access Control
16 MAC extensions, other extensions can be built using the LSM to provide
|
| D | SafeSetID.rst | 4 SafeSetID is an LSM module that gates the setid family of syscalls to restrict
31 This SafeSetID LSM seeks to provide a solution for restricting setid
34 The main use case for this LSM is to allow a non-root program to transition to
37 additional restrictions imposed by this LSM would mean it is a "safer" version
54 as implemented in this LSM, an alternative option would be to simply take away
88 Use an existing LSM
99 This LSM hooks the setid syscalls to make sure transitions are allowed if an
|
| /Linux-v6.1/Documentation/security/ |
| D | lsm-development.rst | 6 a new LSM is accepted into the kernel when its intent (a description of
8 use it) has been appropriately documented in ``Documentation/admin-guide/LSM/``.
9 This allows an LSM's code to be easily compared to its goals, and so
13 For extensive documentation on the available LSM hook interfaces, please
|
| D | lsm.rst | 37 The Linux Security Modules (LSM) project was started by WireX to develop
38 such a framework. LSM was a joint development effort by several security
46 LSM Framework
49 The LSM framework provides a general kernel framework to support
50 security modules. In particular, the LSM framework is primarily focused
54 the infrastructure to support security modules. The LSM framework is
58 `LSM Capabilities Module`_.
60 The LSM framework includes security fields in kernel data structures and
67 The LSM security fields are simply ``void*`` pointers.
98 LSM hooks are maintained in lists. A list is maintained for each
[all …]
|
| D | landlock.rst | 6 Landlock LSM: kernel documentation
21 LSM). Indeed, a Landlock rule shall not interfere with other access-controls
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | procfs-attr-prev | 6 a Linux security module (LSM) active on the system
9 this interface is LSM dependent.
13 this interface are LSM dependent.
14 The format of the data used by this interface is LSM
|
| D | procfs-attr-current | 6 security module (LSM) that is active on the system.
9 of the task identified is LSM dependent.
14 the task identified are LSM dependent.
15 The format of the data used by this interface is LSM
|
| D | procfs-attr-exec | 6 by a Linux security module (LSM) active on the system
10 of the task identified is LSM dependent.
15 the task identified are LSM dependent.
16 The format of the data used by this interface is LSM
|
| D | ima_policy | 9 the policy can be constrained based on LSM specific data.
49 lsm: are LSM specific
126 Examples of LSM specific definitions:
189 either based on a filesystem's UUID (fsuuid) or based on LSM
|
| /Linux-v6.1/Documentation/bpf/ |
| D | prog_lsm.rst | 5 LSM BPF Programs
8 These BPF programs allow runtime instrumentation of the LSM hooks by privileged
16 LSM hook:
20 Other LSM hooks which can be instrumented can be found in
61 * ``"lsm/file_mprotect"`` indicates the LSM hook that the program must
117 Attachment to LSM Hooks
120 The LSM allows attachment of eBPF programs as LSM hooks using :manpage:`bpf(2)`
124 The program can be detached from the LSM hook by *destroying* the ``link``
|
| D | bpf_licensing.rst | 78 Further, some BPF program types - Linux Security Modules (LSM) and TCP
81 registration step of LSM and TCP congestion control modules of the Linux
82 kernel is done through EXPORT_SYMBOL_GPL kernel functions. In that sense LSM
|
| /Linux-v6.1/Documentation/translations/zh_CN/process/ |
| D | 3.Early-stage.rst | 31 模块（LSM）框架中的内核模块；这个模块可以配置为允许特定的应用程序访问实时
35 内核社区来说，这被视为对LSM框架的滥用（LSM框架并不打算授予他们原本不具备的
|
| /Linux-v6.1/Documentation/translations/zh_TW/process/ |
| D | 3.Early-stage.rst | 34 模塊（LSM）框架中的內核模塊；這個模塊可以配置爲允許特定的應用程式訪問實時
38 內核社區來說，這被視爲對LSM框架的濫用（LSM框架並不打算授予他們原本不具備的
|
| /Linux-v6.1/security/lockdown/ |
| D | Kconfig | 6 Build support for an LSM that enforces a coarse kernel lockdown
10 bool "Enable lockdown LSM early in init"
13 Enable the lockdown LSM early in boot. This is necessary in order
|
| /Linux-v6.1/scripts/selinux/ |
| D | README | 1 Please see Documentation/admin-guide/LSM/SELinux.rst for information on
|
| /Linux-v6.1/Documentation/userspace-api/ebpf/ |
| D | index.rst | 10 (LSM).
|
| /Linux-v6.1/security/yama/ |
| D | Kconfig | 12 Documentation/admin-guide/LSM/Yama.rst.
|
| /Linux-v6.1/security/safesetid/ |
| D | Kconfig | 8 SafeSetID is an LSM module that gates the setid family of syscalls to
|
| /Linux-v6.1/Documentation/networking/ |
| D | secid.rst | 4 LSM/SeLinux secid
|
| /Linux-v6.1/Documentation/translations/zh_CN/admin-guide/ |
| D | index.rst | 106 * LSM/index
|
| /Linux-v6.1/security/ |
| D | Kconfig | 119 int "Low address space for LSM to protect from user allocation"
133 systems running LSM.
214 prompt "First legacy 'major LSM' to be initialized"
247 config LSM config
|
| /Linux-v6.1/Documentation/translations/zh_TW/admin-guide/ |
| D | index.rst | 105 LSM/index
|
123
