How are Provisioning and Quoting Enclaves launched

How are Provisioning and Quoting Enclaves launched

I understand that Provisioning Enclave (PvE) is a special enclave. Please clarify the following questions.

  1. How is the PvE launched?
  2. What does it mean that it is provided by Intel? Specifically, is there a  priviliged software (provided/used by Intel) that creates and launches PvE, and that is somehow not accessible to application developers? I am assuming that sgx_create_enclave() cannot be used to create this special enclave.
  3. Is that a software run enclave or a microcode run?
  4. I have similar questions for Quoting Enclave too. How is this launched?
3 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Hi AB.

To find out answer of these questions, I advise that you can read the source code of PSW. All the achitecture build-in enclaves are inside the PSW package.

Regars

you

Architectural enclaves are loaded by the aesm service "when needed". That means PvE is loaded during the EPID join process, QE is loaded the first time you request a quote etc.

Architectural enclaves are signed by a special Intel key that is privileged (CPU/microcode checks the signature and only allows enclaves signed with this key to be privileged). Documentation mentions possibility for custom Launch Enclaves (not signed by Intel), but this currently is not possible as far as I know.

Leave a Comment

Please sign in to add a comment. Not a member? Join today