The attestation encompasses the certificate's hash used for servicing the request. The administrator can establish a secure TLS channel into the enclave with remote attestation by verifying the attestation using the received peer certificate.
Upon successfully delivering a specified number of quotes to external users (currently set to one), the premain process terminates and triggers the execution of the vault. The vault, in turn, utilizes the previously generated certificate for subsequent secure communication.
The vault is configured to rely on this particular certificate for trust verification, utilizing the previously attested channel. Subsequent unsealing of the vault operator is performed confidentially and can potentially be automated.
It is worth noting that incorporating the premain logic into the plugin for enhanced flexibility is not feasible without modifying the vault's source code. This limitation arises because plugins are only loaded after unsealing, which already necessitates a secret.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.enclaive.cloud/confidential-cloud/technology-in-depth/intel-sgx/vault-remote-attestation-plug-in/initialization.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
