fix: Improve header serialization#747
Merged
lucasmcdonald3 merged 30 commits intomasterfrom Mar 26, 2025
Merged
Conversation
lucasmcdonald3
changed the title
added 2 commits
March 26, 2025 12:58
Contributor
|
LGTM |
texastony
approved these changes
Mar 26, 2025
Contributor
There was a problem hiding this comment.
Praise: This is very clear; nice.
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
3 participants
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.
Issue #, if available:
Description of changes:
ESDK-Python <4.0.1 would truncate non-ASCII key provider IDs it wrote to message headers.
If a Raw or Custom MasterKeyProvider or Keyring supplied a non-ASCII key provider ID / key namespace,
ESDK-Python would truncate the the key provider ID it wrote to the message's header.
The message can be decrypted by replacing the truncated provider ID with the expected provider ID in decryption code.
Contact AWS for any questions about this approach.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable: