🏃‍♂️Initialization

Vault Initialization Workflow

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.