recovery: enable clients to send encrypted recovery secrets #878
+832
−350
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clients may not want to bring the key material needed to decrypt the recovery secrets, or the recovery secrets themselves, onto machines exposed to the internet.
To enable a recovery workflow where the recovery secrets (or the needed key material) are kept on an airgapped machine, this PR adds a new endpoint to the Coordinator, allowing clients to retrieve an RSA public key generated by the Coordinator for the recovery workflow.
Clients can use this public key to encrypt their shares on the airgapped machine, transfer the encrypted share, and upload it to the Coordinator, where it is decrypted inside the SGX enclave.
Proposed changes
/api/v2/recover/public-keyto retrieve a public key generated for the recovery