Drop loose base64 decoding #658
Merged
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
anakinj
force-pushed
the
drop-loose-base64-decoding
branch
from
37623e0 to
3dcae61
Compare
nicolastemciuc
added a commit
to cedarcode/fido_metadata
that referenced
this pull request
Sep 10, 2025
- Removed trailing newline at the end of the file to comply with stricter base64 decoding.
- ruby-jwt > 2 no longer supports loose base64 input (e.g., padding issues or newline chars).
- See related PR: jwt/ruby-jwt#658
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.
Description
Support only stricter base64 decoding
Checklist
Before the PR can be merged be sure the following are checked: