Skip to content

Commit b1907f9

Browse files
committed
fix(security): Clarify TRNG engine ownership by OPTEE
The SDK by default provides control of TRNG engine to OP-TEE, which also firewalls the associated MMR regions. Document this design choice for clarity. Also include reference of TRNG in security central page. Signed-off-by: Shiva Tripathi <s-tripathi1@ti.com>
1 parent a1acc01 commit b1907f9

3 files changed

Lines changed: 17 additions & 8 deletions

File tree

source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/DTHEv2.rst

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -216,10 +216,12 @@ software only implementation can be compared to the previous test.
216216
Using the True Random Number Generator (TRNG) Hardware Accelerator
217217
******************************************************************
218218

219-
The pre-built kernel included within the SDK already has the OP-TEE TRNG
220-
driver enabled. You do not need any further configuration.
219+
In the default SDK, OP-TEE controls the TRNG engine and firewalls its
220+
hardware registers, blocking outside access. To use TRNG from Linux instead,
221+
disable the OP-TEE driver and enable the RNG node in the Linux device tree.
221222

222-
Verify that the optee-rng driver is loaded:
223+
Using TRNG from OP-TEE requires no further configuration. Verify the optee-rng
224+
driver loads:
223225

224226
.. code-block:: console
225227

source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/SA2UL_OMAP.rst

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -304,8 +304,12 @@ software only implementation can be compared to the previous test.
304304
Using the TRNG Hardware Accelerator
305305
***********************************
306306

307-
The pre built kernel that come with the SDK already has the TRNG driver
308-
built into the kernel. No further configuration is required.
307+
In the default SDK, OP-TEE controls the TRNG engine and firewalls its
308+
hardware registers, blocking outside access. To use TRNG from Linux instead,
309+
disable the OP-TEE driver and enable the RNG node in the Linux device tree.
310+
311+
Using TRNG from OP-TEE requires no further configuration. Verify the optee-rng
312+
driver loads:
309313

310314
.. ifconfig:: CONFIG_crypto in ('sa2ul')
311315

source/linux/Foundational_Components/System_Security/Security_overview.rst

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,8 @@ The following table lists some of the key Security Features:
4949
| **Authenticated Boot** | Verifies each boot component to ensure only authorized | :ref:`auth_boot_guide` |
5050
| | code executes on the device | |
5151
+-------------------------+-----------------------------------------------------------+--------------------------------------+
52-
| **Crypto Acceleration** | Hardware driver support for cryptographic algorithms | :ref:`crypto-accelerator` |
52+
| **Crypto Acceleration** | Hardware driver support for cryptographic algorithms and | :ref:`crypto-accelerator` |
53+
| **and TRNG** | hardware entropy based secure random number generation | |
5354
+-------------------------+-----------------------------------------------------------+--------------------------------------+
5455
| **Key Management** | Tools for secure key provisioning | :ref:`key-writer-lite-label` |
5556
+-------------------------+-----------------------------------------------------------+--------------------------------------+
@@ -81,7 +82,8 @@ The following table lists some of the key Security Features:
8182
| **Authenticated Boot** | Transparent disk encryption using the Linux kernel | :ref:`auth_boot_guide` |
8283
| | device mapper (dm-crypt) for data confidentiality | |
8384
+-------------------------+-----------------------------------------------------------+--------------------------------------+
84-
| **Crypto Acceleration** | Hardware driver support for cryptographic algorithms | :ref:`crypto-accelerator` |
85+
| **Crypto Acceleration** | Hardware driver support for cryptographic algorithms and | :ref:`crypto-accelerator` |
86+
| **and TRNG** | hardware entropy based secure random number generation | |
8587
+-------------------------+-----------------------------------------------------------+--------------------------------------+
8688
| **Secure Storage** | Protection mechanisms for sensitive data | :ref:`secure-storage-with-rpmb` |
8789
+-------------------------+-----------------------------------------------------------+--------------------------------------+
@@ -106,7 +108,8 @@ The following table lists some of the key Security Features:
106108
+-------------------------+-----------------------------------------------------------+--------------------------------------+
107109
| Security Feature | Description | Links |
108110
+=========================+===========================================================+======================================+
109-
| **Crypto Acceleration** | Hardware driver support for cryptographic algorithms | :ref:`crypto-accelerator` |
111+
| **Crypto Acceleration** | Hardware driver support for cryptographic algorithms and | :ref:`crypto-accelerator` |
112+
| **and TRNG** | hardware entropy based secure random number generation | |
110113
+-------------------------+-----------------------------------------------------------+--------------------------------------+
111114
| **Secure Storage** | Protection mechanisms for sensitive data | :ref:`secure-storage-with-rpmb` |
112115
+-------------------------+-----------------------------------------------------------+--------------------------------------+

0 commit comments

Comments
 (0)