> Note: I can't see the libtss2-esys runtime dependency that Tobias mentioned. @Tobias: is this expected, or am I missing some other flag?
Yes, that's correct. The configure script checks for both tss2-sys and tss2-esys, but eventually, only tss2-sys is used (possible that Andreas intended to switch to the latter at some point, but that's currently not the case).
> What do you think?
I totally agree. As I mentioned before, support for TPM 1.2 in strongSwan is basically limited to remote attestation, but since the plugins required for that are currently not shipped, enabling support for it would be pointless.
> Note: I can't see the libtss2-esys runtime dependency that Tobias mentioned. @Tobias: is this expected, or am I missing some other flag?
Yes, that's correct. The configure script checks for both tss2-sys and tss2-esys, but eventually, only tss2-sys is used (possible that Andreas intended to switch to the latter at some point, but that's currently not the case).
> What do you think?
I totally agree. As I mentioned before, support for TPM 1.2 in strongSwan is basically limited to remote attestation, but since the plugins required for that are currently not shipped, enabling support for it would be pointless.