Indifferent to b64url padding in indy-utils #1055
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.
it was found that recent updates to base64 in indy-utils made the codebase less resilient to b64url padding when decoding. Previously we were indifferent to padding when decoding, then a regression was made which made indy-utils REQUIRE padding. This PR fixes the regression such that indy-utils will decode with or without padding.
this is important for utils such as
unpack_message
.according to encryption envelope: https://github.com/hyperledger/aries-rfcs/blob/main/features/0019-encryption-envelope/README.md