Intel® Software Guard Extensions (Intel® SGX)
Discussion board focused on hardware-based isolation and memory encryption to provide extended code protection in solutions.
1467 Discussions

Re: Re:Quote Verification fails with an error 0xe01b (SGX_QL_NO_QUOTE_COLLATERAL_DATA)

ML8
Beginner
758 Views

@JesusG_Intel would it be possible to share more information with us, if not privately? We have the exact same terminal error, there are a few small diff codes, but the same endresult code:

 

Trusted quote verification:
Info: get target info successfully returned.
Info: sgx_qv_set_enclave_load_policy successfully returned.
Info: sgx_qv_get_quote_supplemental_data_size successfully returned.
Error: App: sgx_qv_verify_quote failed: 0xe021
Error: Ecall: Verify QvE report and identity failed. 0xe013
Error: App: Verification completed with Terminal result: a006
Info: Supplemental data version: 0

===========================================

Untrusted quote verification:
Info: sgx_qv_get_quote_supplemental_data_size successfully returned.
Error: App: sgx_qv_verify_quote failed: 0xe021
Error: App: Verification completed with Terminal result: a006
Info: Supplemental data version: -1081753840

0 Kudos
4 Replies
JesusG_Intel
Moderator
751 Views

Hello ML8,


Are you using production or pre-production CPUs? QuoteVerification will fail on pre-production CPUs.


Sincerely,

Jesus G.

Intel Customer Support


0 Kudos
ML8
Beginner
748 Views

I am using a production CPU on a brand new server.

 

I think its a dependancy problem and a BIOS. We found the bug, but we are unclear what part we did sovled the dependancy issue (service / settings required)

0 Kudos
JesusG_Intel
Moderator
745 Views

Hello ML8,


I'm glad to know you resolved your issue. Would you mind summarizing the steps you took to solve the issue? It may help other users and we may be able to identify what you did specifically that solved it.


Regards,

Jesus G.

Intel Customer Support


0 Kudos
ML8
Beginner
742 Views

My collegue send it to the vendor, to have their support look at the bugs and solve them (upstream if needed).  Generally i would say not to start using workarrounds, but if the vendor doesn't solve them (which i doubt) we can post all the text here.

0 Kudos
Reply