Extend serialized record encoding to allow for multiple encryption keys #3522
Conversation
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
MMcM
force-pushed
the
serializer-keys
branch
3 times, most recently
from
31c2a95 to
bcb1829
Compare
Use varint encoding for prefix.
Default implementation is unchanged.
MMcM
force-pushed
the
serializer-keys
branch
2 times, most recently
from
b3196ad to
a79b153
Compare
It's hard to get to 100% because of some double checking at build and encrypt time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A key number is encoded in the serialized record, in a format that is backward compatible. An interface can be provided to resolve key numbers into keys for encryption and decryption. Existing data has key number 0.