Skip to content

[RFE] Hide the underlying tss_esapi error logs #65

@Xynnn007

Description

@Xynnn007

Current situation

Now we can see the error logs of tss_esapi when using az-cvm-vtpm for platforms not supporting vtpm. See the link for example

ERROR:tcti:src/tss2-tcti/tcti-device.c:452:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:154:tcti_from_file() Could not initialize TCTI file: device 
ERROR:tcti:src/tss2-tcti/tctildr.c:428:Tss2_TctiLdr_Initialize_Ex() Failed to instantiate TCTI 
[2024-12-02T05:44:35Z ERROR tss_esapi::tcti_ldr] Error when creating a TCTI context: response code not recognized
ERROR:tcti:src/tss2-tcti/tcti-device.c:452:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:154:tcti_from_file() Could not initialize TCTI file: device 
ERROR:tcti:src/tss2-tcti/tctildr.c:428:Tss2_TctiLdr_Initialize_Ex() Failed to instantiate TCTI 

Impact

This would bring extra error information for users that sometimes confused.

Ideal future situation

Only raise a piece of log of error or warn level to indicate that underlying tpm/tss is not configured properly. Other logs could be put to trace or debug level.

Implementation options

None

Additional information

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions