coordinator: use random key for intermediate CA #732
Merged
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.
When we introduced Coordinator recovery, we decided to derive all key material deterministically from the seed. This implies that whoever owns the seed can derive these keys offline, too. However, since the seed needs to be held by the workload owner for recovery, the data owner can't trust in the mesh CA cert without trusting the workload owner.
This PR reverts to a random mesh/intermediate key, which is inaccessible to the workload owner. The trade-off is that the mesh key changes after recovery, and all workloads need to be restarted in order to pick up this change.