[crypto]: add KEK for encrypting DEKs#237
Open
pseudomuto wants to merge 1 commit into
Open
Conversation
Adds a KEK interface representing a customer-managed Key Encryption Key (e.g. AWS/GCP KMS) and a KEKEncryptor that wraps a current KEK plus any retired KEKs. New DEKs are always encrypted with the current key, but retired keys remain registered in a by-ID lookup map so DEKMaterial produced before a rotation can still be opened. This is the second half of the envelope-encryption pair started in the prior DEK commit (#236). A no-op (nilKEK) is used when no key is supplied so callers can wire up the encryptor unconditionally and decide later whether to attach a real KEK.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a KEK interface representing a customer-managed Key Encryption Key (e.g. AWS/GCP KMS) and a KEKEncryptor that wraps a current KEK plus any retired KEKs. New DEKs are always encrypted with the current key, but retired keys remain registered in a by-ID lookup map, so DEKMaterial produced before a rotation can still be opened. This is the second half of the envelope-encryption pair started in the prior DEK commit (#236).
A no-op (nilKEK) is used when no key is supplied, so callers can wire up the encryptor unconditionally and decide later whether to attach a real KEK.