Andreas Fuchs

Ok, so instead of loading the tcti-device it loads the tctildr recurively. ``` debug:tcti:/var/tmp/portage/app-crypt/tpm2-tss-4.1.1-r1/work/tpm2-tss-4.1.1/src/tss2-tcti/tctildr-dl.c:255:tctildr_get_default() Attempting to connect using standard TCTI: Access libtss2-tcti-device.so.0 with /dev/tpmrm0 trace:tcti:/var/tmp/portage/app-crypt/tpm2-tss-4.1.1-r1/work/tpm2-tss-4.1.1/src/tss2-tcti/tctildr-dl.c:131:tcti_from_file() Attempting to load TCTI file:...

That makes no sense... What does the strace say ? ``` strace -e file tpm2_getrandom --hex 5 2>&1| grep open ```

Ok, so my current suspicion is the following: `Tss2_Tcti_Info()` is supposed to return a pointer to a struct. In all of our tcti implementations, this struct is called `tss2_tcti_info`. Now...

So I did setup a KVM with a Gentoo livecd from today and a stage3 from today. I did `emerge clang` which install clang 17 I used clang17 to build...

> We might have to use `dlmopen(LM_ID_NEWLM, file_xfrm, RTLD_NOW);`, see the [man pages](https://man7.org/linux/man-pages/man3/dlopen.3.html): I always thought, that this was covered by ``` RTLD_GLOBAL The symbols defined by this shared object...

@salahcoronya I was able to reproduce this in KVM. Could you test the commit in the linked PR ? I'd then immediately roll a 4.1.3 release for you.

Fixed by #2771 by checking for recent enough version of json-c

export TSS2_LOG=tcti+trace and run it again. This way we can see the log of the interaction and know better what is freezing.

The FAPI API (i.e. include/tss2/tss2-fapi.h) is designed to work on multiple systems, those with poll() being one of such. The implementation of ifapi-io.c is specific to systems that have poll()....

I would actually prefer to add proper use of the `Tss2_MU_XYZ_Marshal/Unmarshal()` functions instead of having a packed struct. I do not think that there is actually a need for any...