Searched full:trusted (Results 1 – 25 of 102) sorted by relevance
12345
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | tlm,trusted-foundations.yaml | 4 $id: http://devicetree.org/schemas/arm/firmware/tlm,trusted-foundations.yaml#
7 title: Trusted Foundations
10 Boards that use the Trusted Foundations secure monitor can signal its
18 const: trusted-foundations
21 const: tlm,trusted-foundations
25 description: major version number of Trusted Foundations firmware
29 description: minor version number of Trusted Foundations firmware
41 trusted-foundations {
42 compatible = "tlm,trusted-foundations";
|
| D | linaro,optee-tz.yaml | 13 OP-TEE is a piece of software using hardware features to provide a Trusted
37 The method of calling the OP-TEE Trusted OS depending on smc or hvc
|
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 2 Trusted and Encrypted Keys
5 Trusted and Encrypted Keys are two new key types added to the existing kernel
8 stores, and loads only encrypted blobs. Trusted Keys require the availability
17 A trust source provides the source of security for Trusted Keys. This
23 consumer of the Trusted Keys to determine if the trust source is sufficiently
28 (1) TPM (Trusted Platform Module: hardware device)
33 (2) TEE (Trusted Execution Environment: OP-TEE based on Arm TrustZone)
62 environment verified via Secure/Trusted boot process.
80 verifications match. A loaded Trusted Key can be updated with new
88 Relies on Secure/Trusted boot process for platform integrity. It can
[all …]
|
| D | index.rst | 11 trusted-encrypted
|
| D | ecryptfs.rst | 35 time after the unsealing of a 'trusted' key in order to perform the mount in a
49 key-type:= 'trusted' | 'user'
|
| /Documentation/tee/ |
| D | ts-tee.rst | 4 TS-TEE (Trusted Services project)
7 This driver provides access to secure services implemented by Trusted Services.
9 Trusted Services [1] is a TrustedFirmware.org project that provides a framework
15 provides the low level communication for this driver. On top of that the Trusted
17 implementation is provided at [6], which is part of the Trusted Services client
20 All Trusted Services (TS) SPs have the same FF-A UUID; it identifies the TS RPC
26 The generic TEE design is to share memory at once with the Trusted OS, which can
27 then be reused to communicate with multiple applications running on the Trusted
36 Overview of a system with Trusted Services components::
41 | Client | | Trusted |
[all …]
|
| D | amd-tee.rst | 4 AMD-TEE (AMD's Trusted Execution Environment)
12 software-based Trusted Execution Environment (TEE) designed to enable
13 third-party Trusted Applications. This feature is currently enabled only for
25 | Client | | | Trusted |
37 | Client | | subsystem | driver | | Trusted |
53 The TEE commands supported by AMD-TEE Trusted OS are:
55 * TEE_CMD_ID_LOAD_TA - loads a Trusted Application (TA) binary into
64 AMD-TEE Trusted OS is the firmware running on AMD Secure Processor.
|
| D | tee.rst | 4 TEE (Trusted Execution Environment)
12 A TEE is a trusted OS running in some secure environment, for example,
|
| D | op-tee.rst | 4 OP-TEE (Open Portable Trusted Execution Environment)
39 | Client | | Trusted |
50 | API | \/ | subsys | driver | | Trusted OS |
66 OP-TEE provides a pseudo Trusted Application: drivers/tee/optee/device.c in
68 application to retrieve a list of Trusted Applications which can be registered
107 corresponding option in Trusted Firmware for Arm. The Trusted Firmware for Arm
|
| /Documentation/devicetree/bindings/tpm/ |
| D | microsoft,ftpm.yaml | 7 title: Microsoft firmware-based Trusted Platform Module (fTPM)
15 offer trusted computing features in their CPUs aimed at displacing dedicated
16 trusted hardware. Unfortunately, these CPU architectures raise serious
17 challenges to building trusted systems because they omit providing secure
22 those of dedicated trusted hardware.
|
| D | tcg,tpm-tis-mmio.yaml | 7 title: MMIO-accessed Trusted Platform Module conforming to TCG TIS specification
13 The Trusted Computing Group (TCG) has defined a multi-vendor standard
|
| D | tcg,tpm_tis-spi.yaml | 7 title: SPI-attached Trusted Platform Module conforming to TCG TIS specification
13 The Trusted Computing Group (TCG) has defined a multi-vendor standard
|
| D | tcg,tpm-tis-i2c.yaml | 7 title: I²C-attached Trusted Platform Module conforming to TCG TIS specification
13 The Trusted Computing Group (TCG) has defined a multi-vendor standard
|
| /Documentation/userspace-api/ |
| D | tee.rst | 5 TEE (Trusted Execution Environment) Userspace API
22 - TEE_IOC_OPEN_SESSION opens a new session to a Trusted Application.
24 - TEE_IOC_INVOKE invokes a function in a Trusted Application.
28 - TEE_IOC_CLOSE_SESSION closes a session to a Trusted Application.
|
| /Documentation/driver-api/ |
| D | tee.rst | 4 TEE (Trusted Execution Environment) driver API
7 Kernel provides a TEE bus infrastructure where a Trusted Application is
27 Then TEE client driver can talk to a matched Trusted Application using APIs
33 Suppose a TEE client driver needs to communicate with a Trusted Application
|
| /Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 21 user-designated trusted group can share a core. This increase in core sharing
101 trusted (same cookie) at any point in time. Kernel threads are assumed trusted.
110 the idle task is selected. Idle task is globally trusted.
126 priority task is not trusted with respect to the core wide highest priority
127 task. If a sibling does not have a trusted task to run, it will be forced idle
157 and are considered system-wide trusted. The forced-idling of siblings running
166 Core scheduling tries to guarantee that only trusted tasks run concurrently on a
168 concurrently or kernel could be running concurrently with a task not trusted by
173 Core scheduling selects only trusted tasks to run together. IPI is used to notify
207 allowing system processes (trusted tasks) to share a core.
|
| /Documentation/ABI/testing/ |
| D | evm | 13 trusted/encrypted key stored in the Kernel Key
89 as part of the trusted boot. For more information on
90 creating and loading existing trusted/encrypted keys,
92 Documentation/security/keys/trusted-encrypted.rst. Both
|
| D | sysfs-class-bdi | 71 be trusted to play fair.
84 which cannot be trusted to play fair.
112 trusted to play fair, or a nbd device.
|
| D | sysfs-bus-optee-devices | 7 matches Trusted Application (TA) driver and corresponding TA in secure OS. Drivers
|
| /Documentation/filesystems/ |
| D | overlayfs.rst | 103 creation of trusted.* and/or user.* extended attributes, and must provide
149 as a zero-size regular file with the xattr "trusted.overlay.whiteout".
155 A directory is made opaque by setting the xattr "trusted.overlay.opaque"
161 "trusted.overlay.whiteout", should be additionally marked by setting the xattr
162 "trusted.overlay.opaque" to "x" on the merge directory itself.
163 This is needed to avoid the overhead of checking the "trusted.overlay.whiteout"
211 copied up (but not the contents). Then the "trusted.overlay.redirect"
251 upper directory is stored in a "trusted.overlay.upper" extended attribute
371 "trusted.overlayfs.metacopy" xattr which indicates that the upper file
374 the "trusted.overlayfs.metacopy" xattr is removed from the upper file.
[all …]
|
| /Documentation/arch/x86/ |
| D | intel_txt.rst | 5 Intel's technology for safer computing, Intel(R) Trusted Execution
7 provide the building blocks for creating trusted platforms.
35 3_David-Grawrock_The-Front-Door-of-Trusted-Computing.pdf
43 Trusted Boot Project Overview
46 Trusted Boot (tboot) is an open source, pre-kernel/VMM module that
211 Security top-level menu and is called "Enable Intel(R) Trusted
220 system and can also be found on the Trusted Boot site. It is an
|
| /Documentation/admin-guide/device-mapper/ |
| D | verity.rst | 64 and the salt. This hash should be trusted as there is no other authenticity
138 trusted keyring by default, or the secondary trusted keyring if
140 trusted keyring includes by default the builtin trusted keyring, and it can
142 already in the secondary trusted keyring.
|
| /Documentation/security/tpm/ |
| D | index.rst | 2 Trusted Platform Module documentation
|
| /Documentation/devicetree/bindings/firmware/ |
| D | mediatek,geniezone.yaml | 14 providing an isolated execution environment for mTEE (MediaTek Trusted
|
| /Documentation/crypto/ |
| D | asymmetric-keys.rst | 338 1) Restrict using the kernel builtin trusted keyring
343 The kernel builtin trusted keyring will be searched for the signing key.
344 If the builtin trusted keyring is not configured, all links will be
348 2) Restrict using the kernel builtin and secondary trusted keyrings
353 The kernel builtin and secondary trusted keyrings will be searched for the
354 signing key. If the secondary trusted keyring is not configured, this
|
12345