[dgarske]

Description

Extending the new WOLFSSL_OPTEE build option added in #11919 making a trusted OP-TEE application work without a per-project platform file.

• types.h - a WOLFSSL_OPTEE branch in the allocator chain, mapping XMALLOC, XFREE and XREALLOC onto TEE_Malloc, TEE_Free and TEE_Realloc. A trusted application links libutee rather than a C library and has no std heap. TEE_MALLOC_FILL_ZERO, so an allocation never carries another one's bytes. Placed after XMALLOC_OVERRIDE so an explicit override still wins, and shaped like the WOLFSSL_TELIT_M2MB branch beside it, including the WOLFSSL_XFREE_NO_NULLNESS_CHECK variant.
• random.c - a wc_GenerateSeed for WOLFSSL_OPTEE on TEE_GenerateRandom, plus the matching entry in the platform include chain. It seeds the DRBG rather than replacing it, so a build that would rather use the TEE RNG directly can still set CUSTOM_RAND_GENERATE_BLOCK.
• internal.c, tls13.c, benchmark.c - LowResTimer, both TimeNowInMilliseconds variants and current_time from TEE_GetSystemTime, which is monotonic for the life of the trusted application and is not the normal world's clock, so it cannot be steered from outside. settings.h no longer forces USER_TICKS, which existed only because nothing supplied these; a project can still define it to override.
• wc_port.h, wc_port.c - XTIME from TEE_GetREETime. That is the only wall clock a trusted application can reach and the normal world owns it, so it is fit for freshness and logging, not for deciding certificate validity. The WOLFSSL_OPTEE block keeps NO_ASN_TIME for that reason; a port that defines WOLFSSL_OPTEE_ASN_TIME is choosing to trust the rich OS clock, and that is what brings XTIME and the timers into the build.

Testing

Validated on an NVIDIA Jetson Orin Nano (L4T R36.4.4), building the wolfTPM firmware TPM into an OP-TEE trusted application. With these changes the trusted application drops its platform file and its allocator and RNG overrides entirely, and still passes RSA, ECC, AES-CFB, NV, SHA-256, HMAC, PCR and ML-DSA / ML-KEM sign, verify, encapsulate and decapsulate, including the tampered-signature and tampered-ciphertext negative cases.

The TLS and XTIME arms sit behind #ifndef NO_ASN_TIME, which the WOLFSSL_OPTEE block sets, so a default OP-TEE build does not reach them. current_time in benchmark.c is not gated that way, so a trusted application can still be benchmarked without turning certificate dates on. All of them were compiled against the OP-TEE headers with the trusted application toolchain to confirm the TEE API use. TLS has not been run inside a trusted application.

--enable-all builds clean on Linux with WOLFSSL_OPTEE undefined, which is where all of this is inert.

[github-actions]

MemBrowse Memory Report · Explore what changed →

zephyr-frdm_rw612

• FLASH: log_const_area -8 B, rodata -8 B, text +1,600 B (+0.6%, 284,048 B / 67,108,864 B, total: 0% used)

No memory changes detected for:

• gcc-arm-cortex-m0plus
• gcc-arm-cortex-m3
• gcc-arm-cortex-m4
• gcc-arm-cortex-m4-baremetal
• gcc-arm-cortex-m4-crypto-only
• gcc-arm-cortex-m4-dtls13
• gcc-arm-cortex-m4-min-ecc
• gcc-arm-cortex-m4-openssl-compat
• gcc-arm-cortex-m4-pkcs7
• gcc-arm-cortex-m4-pq
• gcc-arm-cortex-m4-rsa-only
• gcc-arm-cortex-m4-sp-math
• gcc-arm-cortex-m4-tls12
• gcc-arm-cortex-m4-tls13
• gcc-arm-cortex-m7
• gcc-arm-cortex-m7-pq
• gcc-arm-cortex-m7-tls13
• stm32-sim-stm32h753

---

_{Catch memory regressions in CI with MemBrowse. Free for open source.}