Repository navigation
Add WOLFSSL_OPTEE for building wolfCrypt into an OP-TEE trusted application - #11919
Merged
Merged
Conversation
|
philljj
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
An OP-TEE trusted application links
libutee, not a C library: no descriptors, sockets, directories or wall clock, and a single thread.settings.h- aWOLFSSL_OPTEEblock besideWOLFSSL_SGX, settingNO_FILESYSTEM,SINGLE_THREADED,NO_ASN_TIMEand the related no-IO options.wc_port.c- adds!defined(WOLFSSL_OPTEE)to the CLOEXEC helper gate, which already excludesWOLFSSL_KERNEL_MODE,WOLFSSL_ZEPHYRandWOLFSSL_SGX.That gate keys off
__unix__, which a Linux cross compiler predefines even for a TA, so the block compiled in and failed on missingfcntl.h.Testing
Validated on an NVIDIA Jetson Orin Nano (L4T R36.4.4): wolfCrypt built into a TA, ML-DSA and ML-KEM run in the secure world and cross-checked on the host. The TA does not build without the macro. Linux default,
--enable-alland--enable-cryptonlybuilds are unaffected;make checkpasses.