__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
# SPDX-License-Identifier: GPL-2.0-only # OP-TEE Trusted Execution Environment Configuration config OPTEE tristate "OP-TEE" depends on HAVE_ARM_SMCCC depends on MMU depends on RPMB || !RPMB help This implements the OP-TEE Trusted Execution Environment (TEE) driver. config OPTEE_INSECURE_LOAD_IMAGE bool "Load OP-TEE image as firmware" default n depends on OPTEE && ARM64 help This loads the BL32 image for OP-TEE as firmware when the driver is probed. This returns -EPROBE_DEFER until the firmware is loadable from the filesystem which is determined by checking the system_state until it is in SYSTEM_RUNNING. This also requires enabling the corresponding option in Trusted Firmware for Arm. The documentation there explains the security threat associated with enabling this as well as mitigations at the firmware and platform level. https://trustedfirmware-a.readthedocs.io/en/latest/threat_model/threat_model.html Additional documentation on kernel security risks are at Documentation/tee/op-tee.rst.
| Name | Type | Size | Permission | Actions |
|---|---|---|---|---|
| Kconfig | File | 1.03 KB | 0644 |
|
| Makefile | File | 318 B | 0644 |
|