Thomas

I found an issue with the patch i sent you. It was not possible to build an application and to link it with libibmtss and libibmtssutils. It was due to some missing #ifndef TPM_TSS_NO_PRINT to disable the build and the declaration of print functions in the library. Please find attached a new version of the patch

I found an issue with the patch i sent you. It was not possible to build an application and to link it with libibmtss and libibmtssutils. It was due to some missing #ifndef TPM_TSS_NO_PRINT to disable the build and the declaration of print functions in the library.

I found an issue with the patch i sent you. It was not possible to build an application and to link it with libibmtss and libibmtssutils. It was due to some missing #ifndef TPM_TSS_NO_PRINT to disable the build in the library of print functions.

I wrote a patch to disable the build of timepacket if nofile option is selected, and to disable utils (for tpm1.2 and tpm2.0) if noprint option is selected.

undefined reference errors with --enable-nofile and --enable-noprint options

Thanks for the answer. I understand, it makes sense. I have an other question about provisoning process. In the case of the communication is encrypted with client/server authentication, is it really necessary for the server to send the AK certificate to the client ? I understood that this certificate can be useful if we have more than one verifier (send this certificate to other verifiers). But if you have only one verifier, what is the goal of this step ? Thanks, Thomas

Hi, I tested your sample Attestation Client Server, it works well !! Everything needed to deploy and understand it can be found in your documentation, thanks a lot !! Now i'm trying to write a production application based on you code. And i have some questions about the peaces of code to rewrite to match as much as possible the TCG specifications. About server client authentication and encrypted communication , do you think ssh tunneling is enough for authentication, or something "bigger" like VPN/IPSec...

Tspi_Context_Close is blocked when it is called a second time in a process. (Missing MUTEX_UNLOCK in get_user_ps_path function)