Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AESM warning "Failed to set logging callback for the quote provider library." #146

Open
0xabu opened this issue Jul 21, 2021 · 4 comments
Open

Comments

@0xabu
Copy link

0xabu commented Jul 21, 2021

Hi,

I just installed az-dcap-client using the Ubuntu 18.04 packages, and it seems to be working correctly, but I noticed these warnings logged repeatedly from the AESM daemon (I am using SGX_AESM_ADDR to perform out-of-proc quote retrieval):

Jul 21 22:25:48 SGX-Temp-Test-VM aesm_service[25583]: [get_qpl_handle ../qe_logic.cpp:295] Failed to set logging callback for the quote provider library.
@oxxenix
Copy link

oxxenix commented Sep 8, 2021

I am having a similar issue in Ubuntu 18.04:

`Warning: Cannot set QPL directory, you may get ECDSA quote with Encrypted PPID cert type.

[get_qpl_handle ../qe_logic.cpp:295] Failed to set logging callback for the quote provider library.[get_qpl_handle ../qe_logic.cpp:295] Failed to set logging callback for the quote provider library`

@csegarragonz
Copy link

I have reported the issue to the SGX repository, as it belongs there: intel/linux-sgx#812

@dimakuv
Copy link

dimakuv commented Apr 26, 2024

Just FYI: we also observe the same problem on MS Azure VMs. The explanation for this iiuc is here: intel/linux-sgx#812.

Basically, Microsoft Azure provides a pre-installed special version of the Quote Provider library. This special version of the library does not have the sgx_ql_set_logging_callback() for whatever reason, and that is exactly what the AESM daemon expects. Interestingly, this Microsoft-Azure-special version of the library has sgx_ql_set_logging_function() -- a suspiciously similar function name. Is this just a mismatch in naming?

An alternative explanation may be that Microsoft-special version of the Quote Provider library uses the AZDCAP_DEBUG_LOG_LEVEL envvar, and so Microsoft relies on its own logging and doesn't want AESM to report any errors? That would be a strange decision, since AESM may report errors unrelated to the Quote Provider...

Also, since I'm here -- is this GitHub repository dead? I see multiple issues that are open for ~2 years, with no explanations by developers or "will fix" messages with no follow ups.

@msft-gumunjal
Copy link
Collaborator

I will take a look at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants